Advisory record · GHSA-6g2r-675j-hx59

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

CVSS 2.3 Low

Published by the GitHub Advisory Database at 2 Oct 2026, 18:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
xxhash-rustcrates.io<0.8.160.8.16
Identifiers
GHSA-6g2r-675j-hx59
Weakness (CWE)
CWE-125
Published
2 Oct 2026
Updated
2 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The xxhash-rust crate, versions before 0.8.16, has an issue in its safe xxh3 custom-secret API: the minimum secret length check is only a debug assertion, so in release builds a secret shorter than the internal minimum, such as an empty one, can lead to an out-of-bounds read. The source describes a Miri report of undefined behavior from a safe call with an empty secret, and gives few details beyond that. Upgrade to xxhash-rust 0.8.16, which is the listed fixed version.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 3.1 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.