---
id: CVE-2026-62335
title: OpenVM's OpenVmHalo2Verifier accepts non-canonical app commitments
summary: >-
  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 `…
severity: medium
cvss: 6.9
cvssVector: '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'
cvssSource: cna
cwe:
  - CWE-20
vendor: openvm-org
product: openvm
affected:
  - openvm < 1.7.0
  - 'openvm >= 2.0.0-alpha, < 2.0.0-rc.3'
  - 'openvm >= 2.1.0-dev.0, < 2.1.0-preview'
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: partial
  timestamp: '2026-11-06T18:01:30.383977Z'
published: '2026-10-30'
updated: '2026-11-06'
sourceUpdated: '2026-11-06T18:02:21.495Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-62335'
references:
  - url: >-
      https://github.com/openvm-org/openvm/security/advisories/GHSA-w82q-w67c-67wv
    label: >-
      https://github.com/openvm-org/openvm/security/advisories/GHSA-w82q-w67c-67wv
  - url: 'https://github.com/openvm-org/openvm/pull/152'
    label: 'https://github.com/openvm-org/openvm/pull/152'
  - url: >-
      https://github.com/openvm-org/openvm/commit/1962276254aabc5420de266a8cb672433ce955ff
    label: >-
      https://github.com/openvm-org/openvm/commit/1962276254aabc5420de266a8cb672433ce955ff
  - url: >-
      https://github.com/openvm-org/openvm/blob/v2.0.0-alpha/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
    label: >-
      https://github.com/openvm-org/openvm/blob/v2.0.0-alpha/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
  - url: >-
      https://github.com/openvm-org/openvm/blob/v2.0.0-beta.2/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
    label: >-
      https://github.com/openvm-org/openvm/blob/v2.0.0-beta.2/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
  - url: >-
      https://github.com/openvm-org/openvm/blob/v2.1.0-dev.0/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
    label: >-
      https://github.com/openvm-org/openvm/blob/v2.1.0-dev.0/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol
  - url: 'https://github.com/openvm-org/openvm/releases/tag/v1.7.0'
    label: 'https://github.com/openvm-org/openvm/releases/tag/v1.7.0'
  - url: 'https://github.com/openvm-org/openvm/releases/tag/v2.0.0-rc.3'
    label: 'https://github.com/openvm-org/openvm/releases/tag/v2.0.0-rc.3'
  - url: 'https://github.com/openvm-org/openvm/releases/tag/v2.1.0-preview'
    label: 'https://github.com/openvm-org/openvm/releases/tag/v2.1.0-preview'
tags:
  - cve.org
epss: 0.00379
epssPercentile: 0.32152
ingestedAt: '2026-11-05T16:24:31.446Z'
---

## Overview

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.

## Affected

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

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.