Advisory

RUSTSEC-2026-0208

Also known as: None

Summary

Potential Panic in AVX2 SHAKE-256

Details

The AVX2-optimized implementation of SHAKE-256 intended for use in
ML-KEM and ML-DSA would panic if the length of the output buffers was
greater than 32 and not a multiple of 8, due to an out-of-bounds
indexing operation.

Impact
This bug impacts users on AVX2 platforms that use the
libcrux_sha3::avx2::x4::shake256 API outside of ML-KEM or ML-DSA
with output buffers of length > 32 and not divisible by 8. It does
not impact the use in ML-KEM or ML-DSA because there output buffer
lengths are always divisible by 8.

Mitigation
Starting from version 0.0.10, the AVX2-optimized SHAKE-256 will no
longer panic on output buffer lengths > 32 that are not divisible by
8.

Severity

Not rated by the source.

Dates

Published
2026-05-21 12:00 UTC
Modified
2026-07-17 11:45 UTC

Affected packages and fixes

libcrux-sha3

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.0.10 (semver)

Fixed versions

0.0.10

Fix

  • Fixed version 0.0.10
    cargo update -p libcrux-sha3 --precise 0.0.10

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences