CVE-2026-62335: openvm · Improper Input Validation
Affects openvmSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium · fixed in 2.1.0-preview : update openvm when convenient.
Data as of 30 Oct 2026, 20:19 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.9 |
|---|
- Patch
- Available – fixed in 2.1.0-preview, 2.0.0-rc.3, 1.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade openvm to 2.1.0-preview, 2.0.0-rc.3 or 1.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| openvm-orgopenvm | Affected
| Fixed in
|
| openvm-orgopenvm | Affected
| Fixed in
|
| openvm-orgopenvm | Affected
| Fixed in
|
AI-suggested
A patch is available and should be applied by upgrading to OpenVM versions 1.7.0, 2.0.0-rc.3, or 2.1.0-preview or later. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with the vendor that their environment is updated accordingly.
Description
CVE-2026-62335 is an improper input validation vulnerability in openvm-org's OpenVM zkVM framework. Versions before 1.7.0 in the 1.x line, and certain prereleases of 2.0 and 2.1, allow the verify function to accept non-canonical 256-bit values for app executable and VM commitments without verifying they are less than the BN254 scalar field modulus. This can cause ambiguity between the byte-level inputs and the field elements used by the verifier. The issue is fixed in versions 1.7.0, 2.0.0-rc.3, and 2.1.0-preview.
References
- github.com/openvm-org/openvm/security/advisories/GHSA-w82q-w67c-67wv (opens in a new tab)
- github.com/openvm-org/openvm/pull/152 (opens in a new tab)
- github.com/openvm-org/openvm/commit/1962276254aabc5420de266a8cb672433ce955ff (opens in a new tab)
- github.com/openvm-org/openvm/blob/v2.0.0-alpha/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol (opens in a new tab)
- github.com/openvm-org/openvm/blob/v2.0.0-beta.2/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol (opens in a new tab)
- github.com/openvm-org/openvm/blob/v2.1.0-dev.0/crates/sdk/contracts/template/OpenVmHalo2Verifier.sol (opens in a new tab)
- github.com/openvm-org/openvm/releases/tag/v1.7.0 (opens in a new tab)
- github.com/openvm-org/openvm/releases/tag/v2.0.0-rc.3 (opens in a new tab)
- github.com/openvm-org/openvm/releases/tag/v2.1.0-preview (opens in a new tab)