xxhash-rust
Implementation of xxhash
Activity
- Latest release
- 1mo ago
- Total releases
- 26
- Cadence
- ~26 days
- Last 12 months
- 4
Details
- License
- BSL-1.0
- First release
- Oct 15, 2020
| Version | Released | |
|---|---|---|
0.8.19
patch
| ||
0.8.18
unknown
| ||
0.8.17
unknown
| ||
0.8.16
unknown
| ||
0.8.15
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.14
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.13
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.12
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.11
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.10
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.9
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.8
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.7
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.6
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.5
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.4
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.3
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.2
unknown
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.1
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.6
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.5
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.4
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.3
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.2
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev | ||
0.8.0-beta.1
unknown
yanked
1 CVE
GHSA-6g2r-675j-hx59
Oct 02, 2026
xxhash-rust: Safe xxh3 custom-secret API accepts too-short secret in release
2.3
/ 10
Low
Local
Low
High
None
Unchanged
Low
None
None
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:
Fixed in
0.8.16
References Updated Oct 02, 2026 · Source: OSV.dev |