openvm-org vulnerabilities and threats

CVE-2026-62333 is a high-severity vulnerability in the openvm-org OpenVM zkVM framework affecting versions prior to 1.7.0 in the 1.x line and certain prereleases of 2.0 and 2.1. The flaw involves improper input validation in the MemoryMerkleAir component, allowing a malicious prover to fabricate a subtree below a memory leaf and alter the committed memory root without corresponding memory operations. This compromises the soundness of OpenVM proofs using persistent memory. The issue is fixed in OpenVM versions 1.7.0, 2.0.0-rc.3, and 2.1.0-preview.

CVE-2026-62334 is a high-severity vulnerability in openvm-org's OpenVM zkVM framework affecting versions prior to 1.7.0 in the 1.x line, and certain prereleases of 2.0 and 2.1. The issue arises from improper verification in the OpenVmHalo2Verifier.verify function, where user-controlled proof data can cause the system to accept arbitrary commitments without proper proof validation. This flaw allows bypassing the intended proof checks by exploiting dispatch to non-verifier functions. The vulnerability is fixed in OpenVM versions 1.7.0, 2.0.0-rc.3, and 2.1.0-preview.

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.

OpenVM is a performant and modular zkVM framework built for customization and extensibility. Prior to version 1.6.0, the openvm-pairing guest library's try_honest_pairing_check function invokes Theorem 3 of https://eprint.iacr.org/2024/640.pdf but does not check that the scaling factor s is in a proper subfield of Fp12. This allows incorrect results to the pairing check. This issue has been patched in version 1.6.0.