Triton VM has a Soundness Vulnerability due to Improper Sampling of Randomness
Priority LOW 38CWE-330Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
In affected versions of Triton VM, the verifier failed to correctly sample randomness in the FRI sub-protocol. Malicious provers can exploit this to craft proofs for arbitrary statements that this verifier accepts as valid, undermining soundness. Protocols that rely on proofs and the supplied verifier of the affected versions of Triton VM are completely broken. Protocols implementing their own verifier might be unaffected. The flaw was corrected in commit 3a045d63, where the relevant randomness is sampled correctly.
Why it matters now
Fix Fixed triton-vm (crates.io): 2.0.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | triton-vm (crates.io) | 0.41.0 to before 2.0.0 | 2.0.0 | Patch available | GHSA-rjr4-v43m-pxq6 |
- triton-vm (crates.io) Vendor— Affected 0.41.0 to before 2.0.0 Fixed in 2.0.0 Patch available GHSA-rjr4-v43m-pxq6
Remediation
- Fix · GHSA-rjr4-v43m-pxq6 triton-vm (crates.io) Fixed in 2.0.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-rjr4-v43m-pxq6
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences