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.