Skip to content
Fencer Intel
high 7.5

CVE-2026-76234 json

libcrux before 0.0.6 Cryptographic Implementation Bug Fixes

published 9mo ago modified 15d ago also GHSA-435g-fcv3-8j26 , RUSTSEC-2026-0023 , RUSTSEC-2026-0024 , RUSTSEC-2026-0025 , RUSTSEC-2026-0026 , EUVD-2026-62475

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

libcrux-ecdh and libcrux-ed25519 before 0.0.6, and libcrux-psq before 0.0.7, contain cryptographic implementation bugs. libcrux-ecdh did not properly check length and clamping during X25519 secret validation (and had a broken clamping check for imported X25519 secret keys); libcrux-ed25519 performed a duplicated clamping step during key generation; and libcrux-psq panicked instead of propagating an AEADError. These were fixed in the respective patched releases.

Patch / fix

  • crates.io libcrux-ecdh 0.0.6
  • crates.io libcrux-ed25519 0.0.6
  • crates.io libcrux-psq 0.0.7
  • celabshq libcrux-ecdh 0.0.6
  • celabshq libcrux-ed25519 0.0.6
  • celabshq libcrux-psq 0.0.7

Is CVE-2026-76234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-76234 updated cvss 7.5

libcrux-ecdh: libcrux-ed25519: libcrux-psq: libcrux: Cryptographic implementation bugs lead to Denial of Service

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
crates.io libcrux-ecdh
<0.0.6
>=0.0.0-0, <0.0.6
0.0.6
crates.io libcrux-ed25519
<0.0.6
>=0.0.0-0, <0.0.6
0.0.6
crates.io libcrux-psq
<0.0.7
>=0.0.0-0, <0.0.7
0.0.7

Affected products

  • celabshq libcrux-ecdh
  • celabshq libcrux-ed25519
  • celabshq libcrux-psq

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature
  • CWE-20 Improper Input Validation
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.