GHSA-265x-v3qf-ff6p

Suggest an improvement
Source
https://github.com/advisories/GHSA-265x-v3qf-ff6p
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-265x-v3qf-ff6p/GHSA-265x-v3qf-ff6p.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-265x-v3qf-ff6p
Aliases
Published
2026-11-18T16:13:34Z
Modified
2026-11-18T16:30:05Z
Severity
  • 6.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
snark-verifier accepts non-canonical KZG accumulator limb encodings
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.

Database specific
{
    "cwe_ids":  [
        "CWE-1284",
        "CWE-20"
    ],
    "github_reviewed":  true,
    "github_reviewed_at":  "2026-11-18T16:13:34Z",
    "nvd_published_at":  "2026-10-30T20:17:10Z",
    "severity":  "MODERATE"
}
References

Affected packages

crates.io / snark-verifier

Package

Name
snark-verifier
View open source insights on deps.dev
Purl
pkg:cargo/snark-verifier

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
0.2.5

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-265x-v3qf-ff6p/GHSA-265x-v3qf-ff6p.json"