PoC Monitor
← All CVEs
CVE-2026-62334published 30 Oct 2026 20:06 UTCData: JSON · API

OpenVM

OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification

OpenVM is a performant and modular zkVM framework built for customization and extensibility. Before 1.7.0 in the 1.x line and in affected 2.0 and 2.1 prereleases, `OpenVmHalo2Verifier.verify` constructs raw proof calldata from user-controlled `proofData`, performs a `staticcall` to `address(this)`, and treats a successful call as proof acceptance. If the first four proof bytes match another external selector exposed by the wrapper, dispatch can invoke a successful non-verifier function instead of the generated Halo2 fallback verifier. Applications using the generated Solidity wrapper can consequently accept arbitrary app commitments and public values without checking the proof suffix, accumulator, app commitments or public values. This issue is fixed in versions 1.7.0, 2.0.0-rc.3 and 2.1.0-preview.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-754
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

openvm-org openvm
  • < 1.7.0
  • >= 2.0.0-alpha, < 2.0.0-rc.3
  • >= 2.1.0-dev.0, < 2.1.0-preview

Fixed in 1.7.0, 2.0.0-rc.3, 2.1.0-preview

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published30 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.