Technical impact
The vulnerability lies in OpenVmHalo2Verifier’s handling of user‑supplied proof data. Rather than validating the proof suffix, accumulator, and public values, the contract constructs calldata from the raw input, staticcalls itself, and treats any successful call as a valid proof. This logic flaw allows an attacker to craft a proofData that triggers a different external function exposed by the wrapper, thereby accepting arbitrary application commitments and public values. The consequence is a logical bypass of proof verification, effectively granting the attacker the ability to forge valid proof operations and compromise the integrity of applications relying on the verifier.
Affected Systems
Affected products are the OpenVM framework from openvm-org, specifically versions before 1.7.0 in the 1.x line and pre‑release versions of 2.0 and 2.1 that include the vulnerable OpenVmHalo2Verifier implementation.
Risk and Exploitability
The CVSS score of 8.7 reflects a high severity, and no EPSS data is available. The vulnerability is not listed in the CISA KEV catalog. Because the exploit can be triggered by any transaction that supplies crafted proofData, the attack vector is effectively remote and requires only standard interaction with the smart contract. The lack of a known exploit but high impact denotes a significant risk, warranting prompt mitigation.