What is GHSA-435G-FCV3-8J26?

GHSA-435G-FCV3-8J26 is a low-severity improper input validation vulnerability in libcrux-ecdh (rust), affecting versions <= 0.0.5. It is fixed in 0.0.6, 0.0.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which packages are affected by GHSA-435G-FCV3-8J26?

libcrux-ecdh (rust) versions <= 0.0.5; libcrux-ed25519 (rust) versions <= 0.0.5; libcrux-psq (rust) versions <= 0.0.6.

Is there a fix for GHSA-435G-FCV3-8J26?

Yes. GHSA-435G-FCV3-8J26 is fixed in 0.0.6, 0.0.7. Upgrade to this version or later.

Is GHSA-435G-FCV3-8J26 exploitable, and should I be worried?

Whether GHSA-435G-FCV3-8J26 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-435G-FCV3-8J26 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-435G-FCV3-8J26 in libcrux-ecdh

Q: Which packages are affected by GHSA-435G-FCV3-8J26?

libcrux-ecdh (rust) versions <= 0.0.5; libcrux-ed25519 (rust) versions <= 0.0.5; libcrux-psq (rust) versions <= 0.0.6.

Q: Is there a fix for GHSA-435G-FCV3-8J26?

Yes. GHSA-435G-FCV3-8J26 is fixed in 0.0.6, 0.0.7. Upgrade to this version or later.

Q: Is GHSA-435G-FCV3-8J26 exploitable, and should I be worried?

Whether GHSA-435G-FCV3-8J26 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-435G-FCV3-8J26 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-435G-FCV3-8J26?

Upgrade: libcrux-ecdh to 0.0.6 or later, libcrux-ed25519 to 0.0.6 or later, libcrux-psq to 0.0.7 or later.

Summary

Bug-Fixes in libcrux-ecdh, libcrux-ed25519, libcrux-psq

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.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

libcrux-ecdh (<= 0.0.5) libcrux-ed25519 (<= 0.0.5) libcrux-psq (<= 0.0.6)

Security releases

libcrux-ecdh → 0.0.6 (rust) libcrux-ed25519 → 0.0.6 (rust) libcrux-psq → 0.0.7 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

libcrux-ecdh to 0.0.6 or later; libcrux-ed25519 to 0.0.6 or later; libcrux-psq to 0.0.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-435G-FCV3-8J26? GHSA-435G-FCV3-8J26 is a low-severity improper input validation vulnerability in libcrux-ecdh (rust), affecting versions <= 0.0.5. It is fixed in 0.0.6, 0.0.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which packages are affected by GHSA-435G-FCV3-8J26?
- libcrux-ecdh (rust) (versions <= 0.0.5)
- libcrux-ed25519 (rust) (versions <= 0.0.5)
- libcrux-psq (rust) (versions <= 0.0.6)
Is there a fix for GHSA-435G-FCV3-8J26? Yes. GHSA-435G-FCV3-8J26 is fixed in 0.0.6, 0.0.7. Upgrade to this version or later.
Is GHSA-435G-FCV3-8J26 exploitable, and should I be worried? Whether GHSA-435G-FCV3-8J26 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-435G-FCV3-8J26 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-435G-FCV3-8J26?
- Upgrade libcrux-ecdh to 0.0.6 or later
- Upgrade libcrux-ed25519 to 0.0.6 or later
- Upgrade libcrux-psq to 0.0.7 or later

Summary

libcrux-ecdh

libcrux-ed25519

libcrux-psq