CVE-2026-61618 — snark-verifier
Fix: axiom-crypto/snark-verifier@d6aaf66CVE-2026-61618 is a Improper Input Validation vulnerability in snark-verifier. A fix is available for snark-verifier — see the affected versions and patch details below.
SNARK Verifier: noncanonical accumulator limb decoding
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-61618.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
snark-verifierReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | snark-verifier | all versions | 0.2.5cargo update -p snark-verifier --precise 0.2.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snark-verifier, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update snark-verifier to 0.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-61618 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-61618 in your dependencies?
Find it across crates.io, including transitive dependencies.