openvm-org OpenVM up to 1.6.x Solidity Wrapper OpenVmHalo2Verifier.verify appExeCommit/appVmCommit input validation

Summaryinfo

A vulnerability identified as critical has been detected in openvm-org OpenVM up to 1.6.x. This issue affects the function OpenVmHalo2Verifier.verify of the component Solidity Wrapper. The manipulation of the argument appExeCommit/appVmCommit leads to input validation. This vulnerability is traded as CVE-2026-62335. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in openvm-org OpenVM up to 1.6.x. It has been rated as critical. This issue affects the function OpenVmHalo2Verifier.verify of the component Solidity Wrapper. The manipulation of the argument appExeCommit/appVmCommit with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-62335 since 07/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

Upgrading to version 1.7.0, 2.0.0-rc.3 or 2.1.0-preview eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• openvm-org

Name

• OpenVM

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6

Website

• Product: https://github.com/openvm-org/openvm/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion