RUSTSEC-2026-0207 json
Incorrect Output of Incremental Portable SHAKE API on Multiple Squeeze Calls
published 6mo ago modified 3mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The incremental squeeze functions in the portable SHAKE XOF API, when attempting to squeeze an output using multiple calls to `squeeze`, rather than squeezing the full output at once, could output incorrect values. Internally, output blocks that were not completely squeezed were not buffered for the next call to `squeeze`, which would consequently drop bytes of the correct squeeze output if the preceding call requested an output of length in bytes not cleanly divisible by `RATE` (168 for SHAKE128, 136 for SHAKE256).
## Impact This bug impacts users that rely on this XOF API to squeeze output in multiple calls where any of the calls request an output length that is not divisible by `RATE`. It does not impact the use of libcrux-sha3 in libcrux-ml-kem or libcrux-ml-dsa.
## Mitigation Starting from version `0.0.10` the squeeze functions correctly output all squeezed bytes independent of the number of `squeeze` calls and the output lengths requested in each call.
Patch / fix
Is RUSTSEC-2026-0207 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | libcrux-sha3 | >=0.0.0-0, <0.0.10 |
0.0.10 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.