# CVE-2026-76234: RUSTSEC-2026-0026 - Unnecessary clamping of seed reduces seed entropy to 251 bits

Source: https://junglewise.ai/threats/cve-2026-76234-bug-fixes-in-libcrux-ecdh-libcrux-ed25519-libcrux-psq  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-19  
License: CC BY 4.0 with a link back

CVE-2026-76234 · Severity: high · CVSS 7.5 · Published 2026-08-19

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.

Technologies: [libcrux-ed25519 (crates.io)](https://junglewise.ai/threats/technologies/libcrux-ed25519). Vendors: [crates.io](https://junglewise.ai/threats/vendors/crates-io).

## Quick answers

**Is CVE-2026-76234 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-76234 being exploited in the wild.

**How severe is CVE-2026-76234?** High severity, with a CVSS score of 7.5, published 19 August 2026.

**Which products and versions are affected?** libcrux-ecdh (crates.io) SEMVER:introduced=0,fixed=0.0.6, SEMVER:introduced=0.0.0-0,fixed=0.0.6; libcrux-ed25519 (crates.io) SEMVER:introduced=0,fixed=0.0.6, SEMVER:introduced=0.0.0-0,fixed=0.0.6; libcrux-psq (crates.io) SEMVER:introduced=0,fixed=0.0.7, SEMVER:introduced=0.0.0-0,fixed=0.0.7.

**Is there a fix for CVE-2026-76234?** Yes. libcrux-ecdh (crates.io): upgrade to 0.0.6 or later; libcrux-ed25519 (crates.io): upgrade to 0.0.6 or later; libcrux-psq (crates.io): upgrade to 0.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-76234?** Check whether you run libcrux-ecdh (crates.io), libcrux-ed25519 (crates.io) or libcrux-psq (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- libcrux-ecdh (crates.io): upgrade to 0.0.6 or later

  ```sh
  cargo update -p libcrux-ecdh
  ```

- libcrux-ed25519 (crates.io): upgrade to 0.0.6 or later

  ```sh
  cargo update -p libcrux-ed25519
  ```

- libcrux-psq (crates.io): upgrade to 0.0.7 or later

  ```sh
  cargo update -p libcrux-psq
  ```


## Affected products

- libcrux-ecdh (crates.io) SEMVER:introduced=0,fixed=0.0.6, SEMVER:introduced=0.0.0-0,fixed=0.0.6
- libcrux-ed25519 (crates.io) SEMVER:introduced=0,fixed=0.0.6, SEMVER:introduced=0.0.0-0,fixed=0.0.6
- libcrux-psq (crates.io) SEMVER:introduced=0,fixed=0.0.7, SEMVER:introduced=0.0.0-0,fixed=0.0.7

## Identifiers

- CVE-2026-76234
- GHSA-435g-fcv3-8j26
- RUSTSEC-2026-0023
- RUSTSEC-2026-0024
- RUSTSEC-2026-0025
- RUSTSEC-2026-0026

## Related threats

- [libcrux has All-Zero Key Generation Upon Catastrophic RNG Failure](https://junglewise.ai/threats/libcrux-has-all-zero-key-generation-upon-catastrophic-rng-failure-3a4b1033)
- [RUSTSEC-2026-0075 - All-Zero Key Generation on Catastrophic RNG Failure](https://junglewise.ai/threats/rustsec-2026-0075-all-zero-key-generation-on-catastrophic-rng-failure-6eab7741)