What is GHSA-6G2R-675J-HX59?

GHSA-6G2R-675J-HX59 is a low-severity out-of-bounds read vulnerability in xxhash-rust (rust), affecting versions < 0.8.16. It is fixed in 0.8.16. A read operation accesses a memory location beyond the intended buffer boundary.

How severe is GHSA-6G2R-675J-HX59?

GHSA-6G2R-675J-HX59 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of xxhash-rust are affected by GHSA-6G2R-675J-HX59?

xxhash-rust (rust) versions < 0.8.16 is affected.

Is there a fix for GHSA-6G2R-675J-HX59?

Yes. GHSA-6G2R-675J-HX59 is fixed in 0.8.16. Upgrade to this version or later.

Is GHSA-6G2R-675J-HX59 exploitable, and should I be worried?

Whether GHSA-6G2R-675J-HX59 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-6G2R-675J-HX59 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-6G2R-675J-HX59 in xxhash-rust

Q: How severe is GHSA-6G2R-675J-HX59?

GHSA-6G2R-675J-HX59 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of xxhash-rust are affected by GHSA-6G2R-675J-HX59?

xxhash-rust (rust) versions < 0.8.16 is affected.

Q: Is there a fix for GHSA-6G2R-675J-HX59?

Yes. GHSA-6G2R-675J-HX59 is fixed in 0.8.16. Upgrade to this version or later.

Q: Is GHSA-6G2R-675J-HX59 exploitable, and should I be worried?

Whether GHSA-6G2R-675J-HX59 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-6G2R-675J-HX59 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-6G2R-675J-HX59?

Upgrade xxhash-rust to 0.8.16 or later.

Summary

xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release

I have a minimized safe Rust witness for xxhash-rust 0.8.15.

Safe public route:

xxhash_rust::xxh3::xxh3_64_with_secret(&[0x41], &[])

The caller-side harness contains no unsafe code. Under release execution, the internal minimum custom-secret length predicate is enforced only by debug_assert!. Release-Miri reports construction of a fixed-width reference beyond the empty secret allocation.

Observed diagnostic:

Undefined Behavior: constructing invalid value of type &[u8; 4]: encountered a dangling reference

Local repair evidence: handling custom-secret slices shorter than the internal minimum before fixed-width secret reads makes the same safe short-secret harness pass under Linux release-Miri.

Local artifacts:

vulnerable log: artifacts/logs/W-4332_xxhash_rust_short_secret_miri_release_linux_001.log
repair log: artifacts/logs/differentials/W-4332_xxhash_rust_local_repair_miri_release_linux_001.log
report: artifacts/reports/W-4332_xxhash_rust_short_secret_report.md

Impact

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

GHSA-6G2R-675J-HX59 has a CVSS score of 2.3 (Low). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.8.16); upgrading removes the vulnerable code path.

Affected versions

xxhash-rust (< 0.8.16)

Security releases

xxhash-rust → 0.8.16 (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 xxhash-rust to 0.8.16 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-6G2R-675J-HX59? GHSA-6G2R-675J-HX59 is a low-severity out-of-bounds read vulnerability in xxhash-rust (rust), affecting versions < 0.8.16. It is fixed in 0.8.16. A read operation accesses a memory location beyond the intended buffer boundary.
How severe is GHSA-6G2R-675J-HX59? GHSA-6G2R-675J-HX59 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of xxhash-rust are affected by GHSA-6G2R-675J-HX59? xxhash-rust (rust) versions < 0.8.16 is affected.
Is there a fix for GHSA-6G2R-675J-HX59? Yes. GHSA-6G2R-675J-HX59 is fixed in 0.8.16. Upgrade to this version or later.
Is GHSA-6G2R-675J-HX59 exploitable, and should I be worried? Whether GHSA-6G2R-675J-HX59 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-6G2R-675J-HX59 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-6G2R-675J-HX59? Upgrade xxhash-rust to 0.8.16 or later.