Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0209 json

AES-GCM did not enforce limits on AAD length

published 5mo 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

NIST Special Publication 800-38D specifies that the bit length of the AAD shall not exceed `2^64 - 1` bits. The implementation of AES-GCM in `libcrux-aesgcm` neither enforced this limit for encryption nor for decryption.

## Impact Use of AES-GCM with AAD of length exceeding the prescribed maximum length degrades the authentication security of the GCM tag.

## Mitigation Starting from version `0.0.9` (published as `libcrux-aes@v0.0.9`), limits on the length of the AAD input are enforced, so overlong AAD inputs result in an error on encryption and decryption.

Patch / fix

Is RUSTSEC-2026-0209 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-aesgcm
>=0.0.0-0
 no fix listed

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.