Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.9, published 18 August 2026.
- Which products and versions are affected?
- triton-vm (crates.io) >= 0.42.0-alpha.4, < 4.0.0; TritonVM >=0.42.0-alpha.4, <4.0.0.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-10: Patch commits 17c7ba0a and ef9d9e72 merged Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run triton-vm (crates.io) or TritonVM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an insufficient verification vulnerability (CWE-345) in the Algebraic Intermediate Representation (AIR) constraints of Triton VM. The sponge_absorb_mem instruction was designed to read data from RAM and hash it, but the proof system did not enforce a constraint verifying that data was actually read from the claimed memory location. A malicious prover could generate a valid-looking proof for the instruction without performing the actual memory read operation, allowing them to forge hash proofs. The vulnerability affects versions >= 0.42.0-alpha.4 through < 4.0.0 of the triton-vm crate. Network reachability and no special privileges are required to exploit this in any system using the vulnerable instruction. The flaw was corrected in commits 17c7ba0a and ef9d9e72 by adding the missing RAM read constraint to the AIR.
Affected products
- TritonVM triton-vm >=0.42.0-alpha.4, <4.0.0
Timeline
- 2026-08-18: disclosed
- 2026-06-10: patched: Patch commits 17c7ba0a and ef9d9e72 merged