CVE-2026-62335

OpenVM's OpenVmHalo2Verifier accepts non-canonical app commitments

Published Oct 30, 2026 CVSS 4.0 · 6.9 Medium 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` accepts `appExeCommit` and `appVmCommit` as `bytes32` values without checking that either is less than the `BN254` scalar field modulus. Although public-value and proof-data lengths are checked, callers can provide non-canonical 256-bit encodings greater than or equal to that modulus at the Solidity wrapper boundary. Applications relying on the wrapper can therefore accept non-canonical app executable and app VM commitments, creating ambiguity between the supplied byte-level values and the field elements used by the verifier. This issue is fixed in versions 1.7.0, 2.0.0-rc.3 and 2.1.0-preview.

Analysis

AI-generated

Technical impact

OpenVmHalo2Verifier’s verify function accepts appExeCommit and appVmCommit parameters as raw 32‑byte values without enforcing that they lie below the BN254 field modulus. Because these values are not validated by the Solidity wrapper, callers can supply non‑canonical 256‑bit encodings that are larger than the scalar field. The verifier then interprets the byte sequence as a field element, making the resulting proof or commitment ambiguous. This ambiguity can lead to inconsistencies in proof validation, potentially causing legitimate proofs to be rejected or invalid proofs to be accepted depending on how the surrounding contract logic behaves. In effect, the integrity of ZK‑VM verification can be compromised.

Affected Systems

The vulnerability affects the openvm‑org OpenVM framework before version 1.7.0 in the 1.x series and in the 2.0 and 2.1 prereleases. The fix is included in releases 1.7.0, 2.0.0‑rc.3, and 2.1.0‑preview and later.

Risk and Exploitability

The CVSS score of 6.9 indicates a medium impact severity. No EPSS data is available, and the vulnerability is not listed in the CISA KEV catalog. Attackers would need the ability to invoke the Solidity wrapper and supply arbitrary 32‑byte values, meaning the exposure is limited to direct contract interactions. Because the issue is a logic flaw rather than an exploit at the network or OS level, the likelihood of widespread exploitation is considered moderate, yet the presence of the flaw creates the potential for integrity violations in applications that rely on the verifier’s correctness.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenVM to a fixed release (1.7.0 or newer, or 2.0.0‑rc.3/2.1.0‑preview).
  • For systems unable to upgrade immediately, inspect all contracts that call OpenVmHalo2Verifier.verify and add input validation to ensure appExeCommit and appVmCommit are less than the BN254 field modulus before invoking the function.
  • Continuously monitor the OpenVM repository and security advisories for future patches or additional mitigating guidance.

Generated by OpenCVE AI on October 30, 2026 at 21:57 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` accepts `appExeCommit` and `appVmCommit` as `bytes32` values without checking that either is less than the `BN254` scalar field modulus. Although public-value and proof-data lengths are checked, callers can provide non-canonical 256-bit encodings greater than or equal to that modulus at the Solidity wrapper boundary. Applications relying on the wrapper can therefore accept non-canonical app executable and app VM commitments, creating ambiguity between the supplied byte-level values and the field elements used by the verifier. This issue is fixed in versions 1.7.0, 2.0.0-rc.3 and 2.1.0-preview.
Title OpenVM's OpenVmHalo2Verifier accepts non-canonical app commitments
Weaknesses CWE-20
References
Metrics cvssV4_0

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

Weaknesses
  • CWE-20

    Improper Input Validation

Sources

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