GHSA-265X-V3QF-FF6P
snark-verifier accepts non-canonical KZG accumulator limb encodings
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 0.2.6 | snark-verifier · -131 d desde divulgación | |
| Divulgación | Publicada | GHSA-265X-V3QF-FF6P divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
### 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.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
crates.iosnark-verifier |
Corregida | 0.2.6 | -131 d | 0.2.8 no afectada |
0.2.50.2.6Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-61618https://github.com/axiom-crypto/snark-verifier/security/advisories/GHSA-265x-v3qf-ff6phttps://github.com/axiom-crypto/snark-verifier/commit/d6aaf66d4706f5317cf61d5dbe00c14e7fbdbb70https://github.com/axiom-crypto/snark-verifierhttps://github.com/axiom-crypto/snark-verifier/releases/tag/v0.2.5Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
