CVE-2026-62334

OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification

Published Oct 30, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability lies in OpenVmHalo2Verifier’s handling of user‑supplied proof data. Rather than validating the proof suffix, accumulator, and public values, the contract constructs calldata from the raw input, staticcalls itself, and treats any successful call as a valid proof. This logic flaw allows an attacker to craft a proofData that triggers a different external function exposed by the wrapper, thereby accepting arbitrary application commitments and public values. The consequence is a logical bypass of proof verification, effectively granting the attacker the ability to forge valid proof operations and compromise the integrity of applications relying on the verifier.

Affected Systems

Affected products are the OpenVM framework from openvm-org, specifically versions before 1.7.0 in the 1.x line and pre‑release versions of 2.0 and 2.1 that include the vulnerable OpenVmHalo2Verifier implementation.

Risk and Exploitability

The CVSS score of 8.7 reflects a high severity, and no EPSS data is available. The vulnerability is not listed in the CISA KEV catalog. Because the exploit can be triggered by any transaction that supplies crafted proofData, the attack vector is effectively remote and requires only standard interaction with the smart contract. The lack of a known exploit but high impact denotes a significant risk, warranting prompt mitigation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the OpenVM SDK to at least version 1.7.0, 2.0.0‑rc.3, or 2.1.0‑preview, which contain the fixed verifier logic.
  • Ensure any deployed wrapper contracts are reconstructed or redeployed using the patched OpenVmHalo2Verifier version to remove the bypass.
  • Audit existing contracts that rely on proof verification for potential misuse of the old verifier before and after applying the patch.

Generated by OpenCVE AI on October 30, 2026 at 21:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Openvm-org
Openvm-org openvm
Vendors & Products Openvm-org
Openvm-org openvm
Type Values Removed Values Added
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.
Title OpenVM's OpenVmHalo2Verifier self-call can bypass proof verification
Weaknesses CWE-754
References
Metrics cvssV4_0

{'score': 8.7, 'vector': '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'}

Weaknesses
  • CWE-754

    Improper Check for Unusual or Exceptional Conditions

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 10:13 PM
Reserved
Jul 13, 2026, 9:42 PM
Status
Deferred
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 2, 2026, 7:35 PM