RUSTSEC-2026-0004 (GHSA-RJR4-V43M-PXQ6)
Vulnerability from osv_rustsec – Published: 2026-01-21 12:00 – Updated: 2026-01-23 05:50 – Source websiteIn 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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [
"crypto-failure"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"triton_vm::verify"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "triton-vm",
"purl": "pkg:cargo/triton-vm"
},
"ranges": [
{
"events": [
{
"introduced": "0.41.0"
},
{
"fixed": "2.0.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-rjr4-v43m-pxq6"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "In affected versions of Triton VM, the verifier failed to correctly sample randomness in the FRI sub-protocol.\n\nMalicious provers can exploit this to craft proofs for arbitrary statements that this verifier accepts as valid, undermining soundness.\n\nProtocols 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.\n\nThe flaw was corrected in commit 3a045d63, where the relevant randomness is sampled correctly.",
"id": "RUSTSEC-2026-0004",
"modified": "2026-01-23T05:50:29Z",
"published": "2026-01-21T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/triton-vm"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0004.html"
}
],
"related": [],
"severity": [],
"summary": "Triton VM Soundness Vulnerability due to Improper Sampling of Randomness"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.