Advisory

RUSTSEC-2026-0329

Also known as: None

Summary

Auto-Reseeding HMAC-DRBG could panic for some output lengths

Details

The automatically reseeding implementations of HMAC-DRBG would panic if called with a desired non-zero output length cleanly divisible by 65_536, the maximum number of output bytes that can be generated before reseeding has to happen.

Impact

An application relying on libcrux-hmac-drgb to provide randomness of byte length a non-zero integer multiple of 65_536 in a single call to fill_bytes would panic.

Any calls with output buffer lengths not cleanly divisible by 65_536 are not affected.

Mitigation

With release the release of version 0.0.2 of libcrux-hmac-drbg this bug has been fixed and reseeding DRBG implementations can be used with arbitrary output lengths.

We recommend users upgrade to libcrux-hmac-drbg version 0.0.2.

Severity

Not rated by the source.

Dates

Published
2026-08-03 12:00 UTC
Modified
2026-10-07 08:30 UTC

Affected packages and fixes

libcrux-hmac-drbg

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.0.2 (semver)

Fixed versions

0.0.2

Fix

  • Fixed version 0.0.2
    cargo update -p libcrux-hmac-drbg --precise 0.0.2

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