Vulnerability RUSTSEC-2026-0428
Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
15 hours ago
October 30, 2026 at 12:00 PM UTC
BLAKE2b produces wrong tag when using `reset()` with a different-length key
0.1.0 - 0.17.15 and 0.18.0-rc.1 - 0.18.0
0.1.0 - 0.17.15 and 0.18.0-rc.1 - 0.18.0
Summary
BLAKE2b produces wrong tag when using `reset()` with a different-length key
Details
Summary
hazardous::mac::blake2b::Blake2b::reset() does not correctly reset the state when a key is supplied that has a different length than the one used upon initialization with hazardous::mac::blake2b::Blake2b::new(), because it errorneously uses a cached length.
Impact
Initialization hazardous::mac::blake2b::Blake2b with a key of some length N, followed by a reset with a key of length != N will produce an incorrect BLAKE2b tag, causing hazardous::mac::blake2b::Blake2b::verify() to fail. This means under honest protocol conditions, parties could experience failing tag verifications.
Resolution
Upgrade to v0.17.16 or v0.18.1.
Related Vulnerabilities
Other vulnerabilities affecting the same packages
Unknown
15 hours ago
LLVM introduces timing-vulnerable optimizations into ML-KEM and ML-DSA operations intended to be constant-time
0.1.0 - 0.17.15 and 0.18.0-rc.1 - 0.18.0 RUSTSEC-2026-0426
0.1.0 - 0.17.15 and 0.18.0-rc.1 - 0.18.0 RUSTSEC-2026-0426
High Risk
5 years ago
Flaw in streaming state in orion
0.1.0 - 0.11.1 GHSA-gffv-5hr2-f9gj
0.1.0 - 0.11.1 GHSA-gffv-5hr2-f9gj
High Risk
7 years ago
Flaw in streaming state reset() functions can create incorrect results.
0.1.0 - 0.11.1 RUSTSEC-2018-0012
0.1.0 - 0.11.1 RUSTSEC-2018-0012
Impacted packages
Timeline
Published
15 hours ago
October 30, 2026 at 12:00 PM UTC
Fixed (0.17.16)
1 day ago
October 29, 2026 at 11:49 PM UTC
Fixed (0.18.1)
1 day ago
October 29, 2026 at 11:55 PM UTC
Last Modified
16 hours ago
October 30, 2026 at 11:15 AM UTC