How severe is CVE-2026-76234?

No CVSS score has been assigned to CVE-2026-76234 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-76234?

CVE-2026-76234 affects the following packages: libcrux-ecdh (crates.io), libcrux-ed25519 (crates.io), libcrux-psq (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2026-76234?

Update libcrux-ecdh to 0.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-76234 is resolved across your whole dependency graph.

How do I detect CVE-2026-76234 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-ecdh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-76234 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-76234 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-76234 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-76234?

CVE-2026-76234 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-76234?

CVE-2026-76234 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-76234 published, and has it been updated?

CVE-2026-76234 was published on August 19, 2026 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2026-76234 — libcrux-ecdh

Fix: cryspen/libcrux#1301

CVE-2026-76234 is a CWE-347 vulnerability in libcrux-ecdh. A fix is available for libcrux-ecdh — see the affected versions and patch details below.

libcrux before 0.0.6 Cryptographic Implementation Bug Fixes

Also known asGHSA-435g-fcv3-8j26RUSTSEC-2026-0023RUSTSEC-2026-0024RUSTSEC-2026-0025RUSTSEC-2026-0026

Published

Aug 19, 2026

Updated

Oct 29, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-76234.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🦀libcrux-ecdh🦀libcrux-ed25519🦀libcrux-psq

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

In accordance with our security policy for libcrux, we publish a GitHub security advisory for any releases whose CHANGELOG includes bug-fixes, and encourage our users to upgrade. The latest releases of the libcrux-ecdh, libcrux-ed25519 and libcrux-psq crates contain the following bug-fixes:

`libcrux-ecdh`

#1301: Check length and clamping in X25519 secret validation. This is a breaking change since errors are now raised on unclamped X25519 secrets or inputs of the wrong length

`libcrux-ed25519`

#1320: Remove duplicated clamping step during key generation

The issue fixed in #1320 was first reported by Nadim Kobeissi.

`libcrux-psq`

#1319: Propagate AEADError instead of panicking
#1301: Fix broken clamping check for imported X25519 secret keys

The issue fixed in #1319 was first reported by Nadim Kobeissi.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libcrux-ecdh`	all versions	0.0.6`cargo update -p libcrux-ecdh --precise 0.0.6`
🦀crates.io	`libcrux-ed25519`	all versions	0.0.6`cargo update -p libcrux-ed25519 --precise 0.0.6`
🦀crates.io	`libcrux-psq`	all versions	0.0.7`cargo update -p libcrux-psq --precise 0.0.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-ecdh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libcrux-ecdh to 0.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-76234 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

In accordance with our [security policy for `libcrux`](https://github.com/cryspen/libcrux/blob/main/SECURITY.md), we publish a GitHub security advisory for any releases whose CHANGELOG includes bug-fixes, and encourage our users to upgrade. The latest releases of the `libcrux-ecdh`, `libcrux-ed25519` and `libcrux-psq` crates contain the following bug-fixes: ## `libcrux-ecdh` - [#1301](https://github.com/cryspen/libcrux/pull/1301): Check length and clamping in X25519 secret validation. This is a breaking change since errors are now raised on unclamped X25519 secrets or inputs of the wrong len

O3 Security · Impact-Aware SCA

Is CVE-2026-76234 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works