Triton VM Soundness Vulnerability due to Missing Constraint
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (triton-vm 4.0.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io triton-vm
- Affected
- >= 0.42.0-alpha.4, < 4.0.0
- Fixed in
- 4.0.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-vjf8-9fx6-mv6x lists affected ranges: crates.io triton-vm >=0.42.0-alpha.4 <4.0.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-vjf8-9fx6-mv6x lists affected ranges: crates.io triton-vm >=0.42.0-alpha.4 <4.0.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
The instruction spongeabsorbmem 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 spongeabsorbmem 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-vjf8-9fx6-mv6x
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-vjf8-9fx6-mv6x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-vjf8-9fx6-mv6x Advisory: Triton VM Soundness Vulnerability due to Missing Constraint IDs: GHSA-vjf8-9fx6-mv6x Record: https://patchnext.com/advisories/ghsa-vjf8-9fx6-mv6x (revision 3, source checked 26 Oct 2026, 15:43 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: triton-vm 4.0.0. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io triton-vm: affected >= 0.42.0-alpha.4, < 4.0.0; fixed in 4.0.0 ## Suggested inspection (read-only) - crates.io triton-vm: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on triton-vm. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-vjf8-9fx6-mv6x (OSV record GHSA-vjf8-9fx6-mv6x lists affected ranges: crates.io triton-vm >=0.42.0-alpha.4 <4.0.0 (fixed)) - Verified: https://github.com/advisories/GHSA-vjf8-9fx6-mv6x (GitHub-reviewed advisory GHSA-vjf8-9fx6-mv6x lists affected ranges: crates.io triton-vm >=0.42.0-alpha.4 <4.0.0) Commands are suggestions: review each one before running it.
Loading voting…