CVE-2026-61618: snark-verifier accepts non-canonical KZG accumulator limb encodings

Medium

OSV id
GHSA-265x-v3qf-ff6p
Also known as
CVE-2026-61618
Published
Last modified

Affected packages

PackageAffected versionsFixed in
snark-verifier
Cargo
< 0.2.5 0.2.5

How to fix it

Upgrade snark-verifier to 0.2.5 or later.

cargo update -p snark-verifier --precise 0.2.5
  • If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Summary

KZG accumulator public-instance limbs were decoded without consistently enforcing canonical limb bounds before reconstructing elliptic-curve coordinates.

In the generated EVM verifier, accumulator coordinates were reconstructed from public-instance limbs using shifted additions before point validation. The verifier checked the reconstructed point, but did not independently check that every limb was below the configured limb bound before reconstruction.

Details

PlonkProof::read takes accumulator public-instance scalars selected by accumulator_indices and passes them into AccumulatorEncoding::from_repr. For the EVM loader, LimbsEncoding::from_repr forwards those limbs to EvmLoader::ec_point_from_limbs, where each coordinate was reconstructed with shl and add before validate_ec_point was applied. That validation checked the reconstructed affine point, not whether the original limb encoding was canonical.

The native verifier path had a related robustness issue: malformed accumulator limb encodings could reach assertion or unwrap-based decoding and panic instead of returning a verification error.

The affected code is in snark-verifier/src/loader/evm/loader.rs and snark-verifier/src/pcs/kzg/accumulator.rs, specifically EvmLoader::ec_point_from_limbs and LimbsEncoding::from_repr.

Impact

For standard SDK aggregation circuits, accumulator limbs are expected to be constrained by the circuit before reaching the verifier boundary, which limits practical exploitability. The missing verifier-side checks nevertheless allowed non-canonical encodings at the boundary, and the native verifier path could be crashed by malformed accumulator public inputs.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.