CVE-2026-46669

Analyzed Analyzed - Analysis Complete

Pairing Check Bypass in OpenVM Guest Library

Publication date: 2026-06-10

Last updated on: 2026-06-12

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-10

Last Modified

2026-06-12

Generated

2026-07-01

AI Q&A

2026-06-11

EPSS Evaluated

2026-06-30

NVD

CVE-2026-46669

Affected Vendors & Products

Vendor	Product	Version / Range
openvm	openvm	to 1.6.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
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.

Attack-Flow Graph

Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Executive Summary

This vulnerability exists in the openvm-pairing guest library of the OpenVM zkVM framework prior to version 1.6.0. Specifically, the try_honest_pairing_check function invokes a mathematical theorem (Theorem 3 from a referenced paper) but fails to verify that the scaling factor 's' is within a proper subfield of Fp12. This lack of validation can lead to incorrect results during the pairing check process.

Impact Analysis

Because the vulnerability allows incorrect results in the pairing check, it can undermine the integrity and correctness of cryptographic operations relying on this function. This could potentially lead to security weaknesses in systems using the affected OpenVM versions, such as accepting invalid proofs or signatures, which may compromise trustworthiness or security guarantees.

Mitigation Strategies

The vulnerability has been patched in openvm-pairing version 1.6.0. Immediate mitigation involves upgrading the openvm-pairing guest library to version 1.6.0 or later.

Detection Guidance

This vulnerability affects versions of the openvm-pairing guest library prior to 1.6.0, specifically in the try_honest_pairing_check function which lacks proper subfield checks for the scaling factor in pairing operations.

To detect if your system is vulnerable, you should first verify the version of the openvm-pairing library installed. If it is older than 1.6.0, it is vulnerable.

Check the installed version of the openvm-pairing library by running a command like: `dpkg -l | grep openvm-pairing` (on Debian-based systems) or `rpm -qa | grep openvm-pairing` (on RPM-based systems).
If you have access to the source or binaries, inspect the version information or changelogs to confirm the version.

Since the vulnerability is related to a cryptographic function's internal check, there are no direct network detection commands or signatures. Detection relies primarily on version checking and ensuring the patched version (1.6.0 or later) is in use.

Hi! I’m here to help you understand CVE-2026-46669. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70