xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release — GHSA-6G2R-675J-HX59

Summary

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:…

Timeline

Published by source

2026-10-02

Risk context

• Reported severity or threat level: low.
• Reported CVSS score: 2.3 out of 10.
• Review exposure for the affected product or family: rust: xxhash-rust.

Product

rust: xxhash-rust

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source

Evidence and provenance

Canonical advisory ID

GHSA-6G2R-675J-HX59

Source

GitHub

Vendor

GitHub

Published by source

2026-10-02

Last source activity

2026-10-02

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.