CVE-2026-76234
Crypto implementation bugs in libcrux X25519/Ed25519/psq risking key compromise and DoS
Is CVE-2026-76234 being exploited?
Not confirmed. CVE-2026-76234 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.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-76234?
CVE-2026-76234 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-76234?
Yes. A fix has been recorded for CVE-2026-76234. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76234 affect?
CVE-2026-76234 affects libcrux-ecdh < 0.0.6, libcrux-ed25519 < 0.0.6, libcrux-psq < 0.0.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76234?
Update to libcrux-ecdh 0.0.6+, libcrux-ed25519 0.0.6+, libcrux-psq 0.0.7+; rebuild and redeploy.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Improper X25519/Ed25519 handling can produce weak/compromised keys or signature failures; libcrux-psq panics may cause denial of service.
Patch when possible
- affected< 0.0.6
- affected< 0.0.6
- affected< 0.0.7
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.