Advisory record · GHSA-fj2x-735w-74vq

gnark-crypto allows unchecked memory allocation during vector deserialization

CVSS 7.5 High

Published by the GitHub Advisory Database at 30 Oct 2025, 17:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/consensys/gnark-cryptoGo>=0.9.1, <0.18.1 || >=0.19.0, <0.19.20.18.1, 0.19.2
Identifiers
GHSA-fj2x-735w-74vq · GO-2025-4087
Weakness (CWE)
CWE-400
Published
30 Oct 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The gnark-crypto Go package, versions 0.9.1 up to but not including 0.18.1, and 0.19.0 up to but not including 0.19.2, is vulnerable. An attacker who can supply serialized vector data to Vector.ReadFrom() can make it allocate up to about 128 GB from a tiny input, causing out-of-memory crashes and denial of service. Upgrade to gnark-crypto 0.18.1 or 0.19.2. Before deserializing, you can check the first 4 bytes of untrusted input to estimate the allocation size.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.