How severe is GHSA-434v-x5qv-pmh6?

No CVSS score has been assigned to GHSA-434v-x5qv-pmh6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-434v-x5qv-pmh6?

GHSA-434v-x5qv-pmh6 affects the following packages: libcrux-ed25519 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-434v-x5qv-pmh6?

Update libcrux-ed25519 to 0.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-434v-x5qv-pmh6 is resolved across your whole dependency graph.

How do I detect GHSA-434v-x5qv-pmh6 in my crates.io dependencies?

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

How do I mitigate GHSA-434v-x5qv-pmh6 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.

How does O3 Security protect against GHSA-434v-x5qv-pmh6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-434v-x5qv-pmh6 can be triaged on real exposure rather than presence alone.

Is GHSA-434v-x5qv-pmh6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-434v-x5qv-pmh6 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.

When was GHSA-434v-x5qv-pmh6 published, and has it been updated?

GHSA-434v-x5qv-pmh6 was published on March 26, 2026 and was last updated on March 27, 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

GHSA-434v-x5qv-pmh6 — libcrux-ed25519

Fix: cryspen/libcrux#1349

GHSA-434v-x5qv-pmh6 is a security vulnerability in libcrux-ed25519. A fix is available for libcrux-ed25519 — see the affected versions and patch details below.

libcrux has All-Zero Key Generation Upon Catastrophic RNG Failure

Also known asRUSTSEC-2026-0075

Published

Mar 26, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 27, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀libcrux-ed25519

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

Impact

This bug only occurs in the event of a catastrophic failure of the CSPRNG, but would allow anyone to forge signatures under the resulting static signing key.

Mitigation

Instead of silently continuing with an all-zero signing key, starting from version 0.0.7 key generation will error in the case of 100 failed attempts at sampling a valid key.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libcrux-ed25519`	all versions	0.0.7`cargo update -p libcrux-ed25519 --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-ed25519, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libcrux-ed25519 to 0.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-434v-x5qv-pmh6 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-434v-x5qv-pmh6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-434v-x5qv-pmh6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The libcrux-ed25519 key generation samples Ed25519 secret keys from a provided CSPRNG in a loop for up to 100 attempts until a non-zero key is found. If a non-zero key could not be sampled within 100 attempts the key generation function would silently continue with an all-zero buffer as the secret key. ## Impact This bug only occurs in the event of a catastrophic failure of the CSPRNG, but would allow anyone to forge signatures under the resulting static signing key. ## Mitigation Instead of silently continuing with an all-zero signing key, starting from version `0.0.7` key generation will

O3 Security · Impact-Aware SCA

Is GHSA-434v-x5qv-pmh6 in your dependencies?

O3 Security finds GHSA-434v-x5qv-pmh6 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works