cargo package report

Is libcrux-aesgcm safe?

3 known vulnerabilities.

cvss
not scored

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — RUSTSEC-2026-0210, the advisory selected below

// advisories

RUSTSEC-2026-0210

UNKNOWN

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.

Affected
>=0.0.0-0
Fixed in
not stated
Published
2026-07-15
Source
osv

OSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.

Checked 2026-09-22 at 01:48 UTC. The most recent advisory here was published 2026-07-15. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is libcrux-aesgcm safe? cargo package security report | CyberXYZ