What is GHSA-PV9V-5J35-XWCR?

GHSA-PV9V-5J35-XWCR is a high-severity out-of-bounds read vulnerability in libcrux-poly1305 (rust), affecting versions < 0.0.5. It is fixed in 0.0.5. A read operation accesses a memory location beyond the intended buffer boundary.

Which versions of libcrux-poly1305 are affected by GHSA-PV9V-5J35-XWCR?

libcrux-poly1305 (rust) versions < 0.0.5 is affected.

Is there a fix for GHSA-PV9V-5J35-XWCR?

Yes. GHSA-PV9V-5J35-XWCR is fixed in 0.0.5. Upgrade to this version or later.

Is GHSA-PV9V-5J35-XWCR exploitable, and should I be worried?

Whether GHSA-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR in libcrux-poly1305

Q: Which versions of libcrux-poly1305 are affected by GHSA-PV9V-5J35-XWCR?

libcrux-poly1305 (rust) versions < 0.0.5 is affected.

Q: Is there a fix for GHSA-PV9V-5J35-XWCR?

Yes. GHSA-PV9V-5J35-XWCR is fixed in 0.0.5. Upgrade to this version or later.

Q: Is GHSA-PV9V-5J35-XWCR exploitable, and should I be worried?

Whether GHSA-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR?

Upgrade libcrux-poly1305 to 0.0.5 or later.

Summary

libcrux Panics During Standalone MAC Operations

An incorrect constant for the key length in libcrux-poly1305 caused the standalone MAC function libcrux_poly1305::mac to always panic with an out-of-bounds memory access.

Mitigation

Starting from version 0.0.5, the correct value is used for the key length constant.

Impact

Applications wishing to use libcrux-poly1305 as a standalone MAC would experience panics. The use of libcrux-poly1305 in libcrux-chacha20poly1305 is unaffected.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

libcrux-poly1305 (< 0.0.5)

Security releases

libcrux-poly1305 → 0.0.5 (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-poly1305 to 0.0.5 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-PV9V-5J35-XWCR? GHSA-PV9V-5J35-XWCR is a high-severity out-of-bounds read vulnerability in libcrux-poly1305 (rust), affecting versions < 0.0.5. It is fixed in 0.0.5. A read operation accesses a memory location beyond the intended buffer boundary.
Which versions of libcrux-poly1305 are affected by GHSA-PV9V-5J35-XWCR? libcrux-poly1305 (rust) versions < 0.0.5 is affected.
Is there a fix for GHSA-PV9V-5J35-XWCR? Yes. GHSA-PV9V-5J35-XWCR is fixed in 0.0.5. Upgrade to this version or later.
Is GHSA-PV9V-5J35-XWCR exploitable, and should I be worried? Whether GHSA-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR 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-PV9V-5J35-XWCR? Upgrade libcrux-poly1305 to 0.0.5 or later.