Rust advisories / libcrux-intrinsics
Vulnerability HighRUSTSEC-2025-0133 · libcrux-intrinsics
RUSTSEC-2025-0133: Incorrect calculation on aarch64
Short answerA security vulnerability in the libcrux-intrinsics crate: Incorrect calculation on aarch64. GitHub rates it High. Fixed in 0.0.4: update to a fixed version.
| Crate | libcrux-intrinsics |
|---|---|
| Type | Vulnerability (crypto-failure) |
| Affected versions | From 0.0.4 before 0.0.4. |
| Fixed in | 0.0.4 |
| Severity | High (GitHub rating) |
| Published | 2025-12-04 |
| Last changed | 2025-12-06 |
| Also known as | GHSA-2cgv-28vr-rv6j |
What to do
- See which version you have:
cargo tree -i libcrux-intrinsics(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p libcrux-intrinsics. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplelibcrux-intrinsics = "0.0.4") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
On platforms without the core::arch::aarch64::vxarq_u64 intrinsic, an unverified fallback in libcrux-intrinsics v0.0.3 passed incorrect arguments and produced wrong results. This corrupted SHA-3 digests and caused libcrux-ml-kem and libcrux-ml-dsa to sample incorrectly, yielding incorrect shared secrets and invalid signatures.
The issue has been fixed in v0.0.4.
References
- Package: crates.io/crates/libcrux-intrinsics
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0133.html
- Report: github.com/cryspen/libcrux/issues/1220
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?