Is github.com/consensys/gnark 0.13 vulnerable?

Go · 1 release from 0.13.0 to 0.13.0 · latest github.com/consensys/gnark is 0.16.5 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/consensys/gnark 0.13.0, the last 0.13 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2025-57801, CVE-2025-57801. Upgrade to 0.14.0 or later to fix all of them.

Upgrade with:go get github.com/consensys/gnark@v0.14.0

Is your project on an affected github.com/consensys/gnark?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/consensys/gnark 0.13.0

  • LowCVE-2025-57801GO-2025-391229 Aug 2025

    Gnark is vulnerable to signature malleability in EdDSA and ECDSA due to missing scalar checks in github.com/consensys/gnark

    Affected
    <0.14.0
    Fixed in
    0.14.0
  • HighCVE-2025-57801GHSA-95v9-hv42-pwrj22 Aug 2025

    gnark is vulnerable to signature malleability in EdDSA and ECDSA due to missing scalar checks

    Affected
    <0.14.0
    Fixed in
    0.14.0

Which of your client projects are still on github.com/consensys/gnark 0.13?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/consensys/gnark version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/consensys/gnark versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.