CVE-2026-62334
OpenVM is a performant and modular zkVM framework built for …
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` constructs raw proof calldata from user-controlled `proofData`, performs a `staticcall` to `address(this)`, and treats a successful call as proof acceptance. If the first four proof bytes match another external selector exposed by the wrapper, dispatch can invoke a successful non-verifier function instead of the generated Halo2 fallback verifier. Applications using the generated Solidity wrapper can consequently accept arbitrary app commitments and public values without checking the proof suffix, accumulator, app commitments or public values. This issue is fixed in versions 1.7.0, 2.0.0-rc.3 and 2.1.0-preview.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/openvm-org/openvm/blob/v2.0.0-alpha/crates/sdk/contracts/template/OpenVmHalo2Ve
- github.com/openvm-org/openvm/blob/v2.0.0-beta.2/crates/sdk/contracts/template/OpenVmHalo2V
- github.com/openvm-org/openvm/blob/v2.1.0-dev.0/crates/sdk/contracts/template/OpenVmHalo2Ve
- github.com/openvm-org/openvm/commit/751bdb1725254c3268782ddf8df89f19035666e3
- github.com/openvm-org/openvm/pull/151
- github.com/openvm-org/openvm/releases/tag/v1.7.0
- github.com/openvm-org/openvm/releases/tag/v2.0.0-rc.3
- github.com/openvm-org/openvm/releases/tag/v2.1.0-preview
- nvd.nist.gov/vuln/detail/CVE-2026-62334
- cve.org/CVERecord?id=CVE-2026-62334
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.