Gnark out-of-memory during deserialization with crafted inputs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-50354: 0.33% estimated exploitation activity in the next 30 days; percentile 25.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Thanks @pventuzelo for reporting. From the correspondence: Hi, We (Fuzzinglabs & Lambdaclass) found that during deserialization of certain files representing a VerifyingKey, an excessive memory allocation is happening consuming a lot of resources and even triggering a crash with the error fatal error: runtime: out of memory. Please find the details below:

Vulnerability Details - Severity: Critical - DoS - Affected Component: Deserialization

Environment - Compiler Version: go version go1.22.2 linux/amd64 - Distro Version: Ubuntu 24.04.1 LTS - Additional Environment Details: - github.com/consensys/gnark v0.11.0 - github.com/consensys/gnark-crypto v0.14.1-0.20240909142611-e6b99e74cec1

Steps to Reproduce You can download the needed files here: https://drive.google.com/drive/folders/1KQ5I3vv4bUllvqbatGappwbAkIcR2NI?usp=sharing You have to run in a terminal. Running the provided code will result in a memory crash or an extremely large memory allocation, which can be observed using…

Published by the source

31 Oct 2024, 20:37 UTC

Last modified by the source

4 Nov 2024, 13:48 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cph5-3pgr-c82g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-50354

Advisory: Gnark out-of-memory during deserialization with crafted inputs
IDs: CVE-2024-50354, GHSA-cph5-3pgr-c82g
Record: https://patchnext.com/advisories/cve-2024-50354 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/consensys/gnark 0.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/consensys/gnark: affected <= 0.11.0; fixed in 0.11.1

## Suggested inspection (read-only)
- Go github.com/consensys/gnark: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/consensys/gnark.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cph5-3pgr-c82g (GitHub-reviewed advisory GHSA-cph5-3pgr-c82g lists affected ranges: Go github.com/consensys/gnark >=0 <=0.11.0)

Commands are suggestions: review each one before running it.