# gnark-crypto allows unchecked memory allocation during vector deserialization

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

- **Identifiers:** `GHSA-fj2x-735w-74vq` · `GO-2025-4087`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 30 Oct 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/consensys/gnark-crypto` (Go): affected `>=0.9.1, <0.18.1 || >=0.19.0, <0.19.2`; fixed in `0.18.1`, `0.19.2`

## 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fj2x-735w-74vq)

## Sources

- [GitHub Advisory Database: GHSA-fj2x-735w-74vq](https://github.com/advisories/GHSA-fj2x-735w-74vq)
- [OSV: GHSA-fj2x-735w-74vq](https://osv.dev/vulnerability/GHSA-fj2x-735w-74vq)
- <https://github.com/Consensys/gnark-crypto/security/advisories/GHSA-fj2x-735w-74vq>
- <https://github.com/Consensys/gnark-crypto/pull/759>
- <https://github.com/Consensys/gnark-crypto/commit/2e7bf9190a0aac896eeec3876c87c77a35661be7>
- <https://github.com/Consensys/gnark-crypto>
- <https://pkg.go.dev/vuln/GO-2025-4087>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fj2x-735w-74vq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fj2x-735w-74vq/>. Everything for agents: <https://agentprime.io/llms.txt>.
