OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification
Impact
OpenVM versions before 1.7.0 and certain 2.0 and 2.1 prereleases have a weakness where the OpenVmHalo2Verifier can bypass proof verification. An attacker with access to user-controlled proof data can exploit this. The impact is acceptance of arbitrary app commitments and public values without proper checks.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
openvm-org · GitHub_M
openvm
3 ranges
openvm-org · GitHub_M
openvm
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 1.7.0
>= 2.0.0-alpha, < 2.0.0-rc.3
>= 2.1.0-dev.0, < 2.1.0-preview
Other versions: unknown
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-62334View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changes- CVE · CVE-2026-62334
Observed 2026-10-30T22:48:24.890Z · upstream updated 2026-10-30T22:13:55.245Z
Prioritization updated
before
[]
after
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-10-30T21:26:46.463302Z", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "yes" }, { "name": "Technical Impact", "value": "partial" } ] } ]
Large field values are marked as truncated previews. Original source snapshots remain retained.
Showing up to 50 most recent observed changes.