Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0329 json

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

published 3mo ago modified last mo.

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 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`.

Patch / fix

  • crates.io libcrux-hmac-drbg 0.0.2

Is RUSTSEC-2026-0329 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io libcrux-hmac-drbg
>=0.0.0-0, <0.0.2
0.0.2

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.