CVE-2026-46669
OpenVM pre-1.6.0 pairing check may accept invalid s subfield; patched in 1.6.0.
Is CVE-2026-46669 being exploited?
Not confirmed. CVE-2026-46669 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-46669?
CVE-2026-46669 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46669?
Yes. A fix has been recorded for CVE-2026-46669. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46669 affect?
CVE-2026-46669 affects OpenVM openvm-pairing library (pre-1.6.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46669?
Upgrade to v1.6.0+ to fix the issue
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows incorrect pairing verification due to missing subfield check; undermines cryptographic proofs in OpenVM workflows.
Patch when possible
- affected< 1.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.