How severe is GHSA-vjf8-9fx6-mv6x?

No CVSS score has been assigned to GHSA-vjf8-9fx6-mv6x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vjf8-9fx6-mv6x?

GHSA-vjf8-9fx6-mv6x affects the following packages: triton-vm (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-vjf8-9fx6-mv6x?

Update triton-vm to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjf8-9fx6-mv6x is resolved across your whole dependency graph.

How do I detect GHSA-vjf8-9fx6-mv6x in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for triton-vm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vjf8-9fx6-mv6x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-vjf8-9fx6-mv6x actively exploited in the wild?

No public exploit code has been indexed for GHSA-vjf8-9fx6-mv6x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-vjf8-9fx6-mv6x published, and has it been updated?

GHSA-vjf8-9fx6-mv6x was published on August 18, 2026 and was last updated on August 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-vjf8-9fx6-mv6x — triton-vm

Fix: TritonVM/triton-vm@17c7ba0

GHSA-vjf8-9fx6-mv6x is a security vulnerability in triton-vm. A fix is available for triton-vm — see the affected versions and patch details below.

Triton VM Soundness Vulnerability due to Missing Constraint

Also known asRUSTSEC-2021-0156

Published

Aug 18, 2026

Updated

Aug 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 24, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀triton-vm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

The instruction sponge_absorb_mem Triton VM fails to verify that hashed values come from the claimed memory location. Malicious provers can substitute arbitrary data instead of actual memory contents.

Any application using instruction sponge_absorb_mem to hash memory data can be given a proof for a forged hash that doesn't correspond to the actual memory. This breaks the security of memory-based commitments.

The flaw was corrected in commits 17c7ba0a and ef9d9e72 by including the appropriate constraints.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`triton-vm`	≥ 0.42.0-alpha.4&&< 4.0.0	4.0.0`cargo update -p triton-vm --precise 4.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for triton-vm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update triton-vm to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjf8-9fx6-mv6x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The instruction `sponge_absorb_mem` Triton VM fails to verify that hashed values come from the claimed memory location. Malicious provers can substitute arbitrary data instead of actual memory contents. Any application using instruction `sponge_absorb_mem` to hash memory data can be given a proof for a forged hash that doesn't correspond to the actual memory. This breaks the security of memory-based commitments. The flaw was corrected in commits `17c7ba0a` and `ef9d9e72` by including the appropriate constraints.

O3 Security · Impact-Aware SCA

Is GHSA-vjf8-9fx6-mv6x in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works