Summary
Triton VM has a Soundness Vulnerability due to Improper Sampling of Randomness
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.
Impact
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-RJR4-V43M-PXQ6? GHSA-RJR4-V43M-PXQ6 is a low-severity use of insufficiently random values vulnerability in triton-vm (rust), affecting versions >= 0.41.0, < 2.0.0. It is fixed in 2.0.0. Security-sensitive operations rely on values that are predictable or insufficiently random.
- Which versions of triton-vm are affected by GHSA-RJR4-V43M-PXQ6? triton-vm (rust) versions >= 0.41.0, < 2.0.0 is affected.
- Is there a fix for GHSA-RJR4-V43M-PXQ6? Yes. GHSA-RJR4-V43M-PXQ6 is fixed in 2.0.0. Upgrade to this version or later.
- Is GHSA-RJR4-V43M-PXQ6 exploitable, and should I be worried? Whether GHSA-RJR4-V43M-PXQ6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RJR4-V43M-PXQ6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RJR4-V43M-PXQ6? Upgrade
triton-vmto 2.0.0 or later.