What is GHSA-2CGV-28VR-RV6J?

GHSA-2CGV-28VR-RV6J is a high-severity use of a broken or risky cryptographic algorithm vulnerability in libcrux-intrinsics (rust), affecting versions = 0.0.3. It is fixed in 0.0.4. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.

Which packages are affected by GHSA-2CGV-28VR-RV6J?

libcrux-intrinsics (rust) versions = 0.0.3; libcrux-ml-kem (rust) versions = 0.0.3; libcrux-ml-dsa (rust) versions = 0.0.3.

Is there a fix for GHSA-2CGV-28VR-RV6J?

Yes. GHSA-2CGV-28VR-RV6J is fixed in 0.0.4. Upgrade to this version or later.

Is GHSA-2CGV-28VR-RV6J exploitable, and should I be worried?

Whether GHSA-2CGV-28VR-RV6J 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-2CGV-28VR-RV6J 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-2CGV-28VR-RV6J in libcrux-intrinsics

Q: How do I fix GHSA-2CGV-28VR-RV6J?

Upgrade: libcrux-intrinsics to 0.0.4 or later, libcrux-ml-kem to 0.0.4 or later, libcrux-ml-dsa to 0.0.4 or later.

Summary

libcrux incorrectly calculates on aarch64

On platforms without the core::arch::aarch64::vxarq_u64 intrinsic, an unverified fallback in libcrux-intrinsics v0.0.3
passed incorrect arguments and produced wrong results. This corrupted SHA-3 digests and caused libcrux-ml-kem and
libcrux-ml-dsa to sample incorrectly, yielding incorrect shared secrets and invalid signatures.

The issue has been fixed in v0.0.4.

Impact

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

Affected versions

libcrux-intrinsics (= 0.0.3) libcrux-ml-kem (= 0.0.3) libcrux-ml-dsa (= 0.0.3)

Security releases

libcrux-intrinsics → 0.0.4 (rust) libcrux-ml-kem → 0.0.4 (rust) libcrux-ml-dsa → 0.0.4 (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-intrinsics to 0.0.4 or later; libcrux-ml-kem to 0.0.4 or later; libcrux-ml-dsa to 0.0.4 or later

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

Frequently Asked Questions

What is GHSA-2CGV-28VR-RV6J? GHSA-2CGV-28VR-RV6J is a high-severity use of a broken or risky cryptographic algorithm vulnerability in libcrux-intrinsics (rust), affecting versions = 0.0.3. It is fixed in 0.0.4. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
Which packages are affected by GHSA-2CGV-28VR-RV6J?
- libcrux-intrinsics (rust) (versions = 0.0.3)
- libcrux-ml-kem (rust) (versions = 0.0.3)
- libcrux-ml-dsa (rust) (versions = 0.0.3)
Is there a fix for GHSA-2CGV-28VR-RV6J? Yes. GHSA-2CGV-28VR-RV6J is fixed in 0.0.4. Upgrade to this version or later.
Is GHSA-2CGV-28VR-RV6J exploitable, and should I be worried? Whether GHSA-2CGV-28VR-RV6J 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-2CGV-28VR-RV6J 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-2CGV-28VR-RV6J?
- Upgrade libcrux-intrinsics to 0.0.4 or later
- Upgrade libcrux-ml-kem to 0.0.4 or later
- Upgrade libcrux-ml-dsa to 0.0.4 or later