# GHSA-rjr4-v43m-pxq6: Triton VM Soundness Vulnerability due to Improper Sampling of Randomness

> Malicious provers can craft invalid proofs accepted by the Triton VM verifier, breaking protocol soundness for applications relying on this library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jan 2026
- **Also known as:** RUSTSEC-2026-0004

## What is GHSA-rjr4-v43m-pxq6?

GHSA-rjr4-v43m-pxq6 is a vulnerability in triton-vm, published on 21 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-rjr4-v43m-pxq6?

3 open source packages ship an affected version, including triton-vm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `triton-vm` | crates.io | From 0.41.0 | 2.0.0 |
| `triton-vm` | crates.io | From 0.41.0 | 2.0.0 |
| `triton-vm` | crates.io | From 0.41.0 | 2.0.0 |

## How do I fix GHSA-rjr4-v43m-pxq6?

Upgrade triton-vm to 2.0.0 or later.

## Is GHSA-rjr4-v43m-pxq6 being exploited?

There is no known exploitation of GHSA-rjr4-v43m-pxq6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rjr4-v43m-pxq6 and fix it if it is affected.

What it is: GHSA-rjr4-v43m-pxq6 is a vulnerability in triton-vm, published on 21 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-rjr4-v43m-pxq6 in the wild and no public exploit code.

Affected packages and fixed versions:
- triton-vm (crates.io): affected from 0.41.0; fixed in 2.0.0
- triton-vm (crates.io): affected from 0.41.0; fixed in 2.0.0
- triton-vm (crates.io): affected from 0.41.0; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-rjr4-v43m-pxq6/ (Markdown: https://insights.sbomify.com/GHSA-rjr4-v43m-pxq6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rjr4-v43m-pxq6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rjr4-v43m-pxq6/
Summaries are generated and may contain mistakes; the official description above is the record.