CVE-2026-62334highCWE-754

CVE-2026-62334: high-severity vulnerability in openvm-org openvm

OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification

Published

Follow this CVE+ Monitor openvm

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8.7epss 0.5%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
openvm-org · openvm
Related CVEs — openvm-org openvm

In the same product, most dangerous first.

CVE-2025-46723HIGHOpenVM byte decomposition of pc in AUIPC chip can overflowEPSS 0.5%CVE-2026-62333HIGHOpenVM: MemoryMerkleAir allows below-leaf rows to alter memory rootsEPSS 0.4%CVE-2026-62335MEDIUMOpenVM's OpenVmHalo2Verifier accepts non-canonical app commitmentsEPSS 0.4%CVE-2026-46669HIGH`openvm-pairing` pairing check missing proper subfield check on scaling factorEPSS 0.2%