Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0210 json

`libcrux-aesgcm` Renamed to `libcrux-aes`

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

Crate `libcrux-aesgcm` was renamed to `libcrux-aes` and will no longer receive new versions under the name `libcrux-aesgcm`, with the final released version under that name being version `0.0.8`. The original functionality is now provided in crate `libcrux-aes`, where development continues at version `0.0.9`.

Patch / fix

Is RUSTSEC-2026-0210 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.