What is GHSA-Q29P-9PFR-J652?

GHSA-Q29P-9PFR-J652 is a high-severity security vulnerability in libcrux-sha3 (rust), affecting versions < 0.0.8. It is fixed in 0.0.8.

Which versions of libcrux-sha3 are affected by GHSA-Q29P-9PFR-J652?

libcrux-sha3 (rust) versions < 0.0.8 is affected.

Is there a fix for GHSA-Q29P-9PFR-J652?

Yes. GHSA-Q29P-9PFR-J652 is fixed in 0.0.8. Upgrade to this version or later.

Is GHSA-Q29P-9PFR-J652 exploitable, and should I be worried?

Whether GHSA-Q29P-9PFR-J652 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-Q29P-9PFR-J652 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-Q29P-9PFR-J652 in libcrux-sha3

Q: Which versions of libcrux-sha3 are affected by GHSA-Q29P-9PFR-J652?

libcrux-sha3 (rust) versions < 0.0.8 is affected.

Q: Is there a fix for GHSA-Q29P-9PFR-J652?

Yes. GHSA-Q29P-9PFR-J652 is fixed in 0.0.8. Upgrade to this version or later.

Q: Is GHSA-Q29P-9PFR-J652 exploitable, and should I be worried?

Whether GHSA-Q29P-9PFR-J652 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-Q29P-9PFR-J652 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-Q29P-9PFR-J652?

Upgrade libcrux-sha3 to 0.0.8 or later.

Summary

libcrux-sha3: Incorrect output from SHAKE squeeze functions

The incremental squeeze functions in the portable SHAKE XOF API, when attempting to squeeze more than RATE (168 for SHAKE128, 136 for SHAKE256) bytes, performed an additional permutation of the state before producing the first output block, thus discarding the first block of RATE bytes of valid XOF output.

Mitigation

Starting from version 0.0.8 the squeeze functions correctly output all blocks including the first block.

Impact

This bug impacts users that rely on this XOF API to squeeze more than RATE bytes. It does not impact the use of libcrux-sha3 in libcrux-ml-kem or libcrux-ml-dsa.

Affected versions

libcrux-sha3 (< 0.0.8)

Security releases

libcrux-sha3 → 0.0.8 (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 libcrux-sha3 to 0.0.8 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is GHSA-Q29P-9PFR-J652? GHSA-Q29P-9PFR-J652 is a high-severity security vulnerability in libcrux-sha3 (rust), affecting versions < 0.0.8. It is fixed in 0.0.8.
Which versions of libcrux-sha3 are affected by GHSA-Q29P-9PFR-J652? libcrux-sha3 (rust) versions < 0.0.8 is affected.
Is there a fix for GHSA-Q29P-9PFR-J652? Yes. GHSA-Q29P-9PFR-J652 is fixed in 0.0.8. Upgrade to this version or later.
Is GHSA-Q29P-9PFR-J652 exploitable, and should I be worried? Whether GHSA-Q29P-9PFR-J652 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-Q29P-9PFR-J652 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-Q29P-9PFR-J652? Upgrade libcrux-sha3 to 0.0.8 or later.