How severe is GHSA-2cgv-28vr-rv6j?

No CVSS score has been assigned to GHSA-2cgv-28vr-rv6j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2cgv-28vr-rv6j?

GHSA-2cgv-28vr-rv6j affects the following packages: libcrux-intrinsics (crates.io), libcrux-ml-kem (crates.io), libcrux-ml-dsa (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2cgv-28vr-rv6j?

Update libcrux-intrinsics to 0.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cgv-28vr-rv6j is resolved across your whole dependency graph.

How do I detect GHSA-2cgv-28vr-rv6j in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-intrinsics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2cgv-28vr-rv6j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2cgv-28vr-rv6j actively exploited in the wild?

No public exploit code has been indexed for GHSA-2cgv-28vr-rv6j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2cgv-28vr-rv6j published, and has it been updated?

GHSA-2cgv-28vr-rv6j was published on December 4, 2025 and was last updated on February 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

libcrux incorrectly calculates on aarch64GHSA-2cgv-28vr-rv6j

Fix: cryspen/libcrux#1222

GHSA-2cgv-28vr-rv6j is a security vulnerability in libcrux-intrinsics. A fix is available for libcrux-intrinsics — see the affected versions and patch details below.

Also known asRUSTSEC-2025-0133

Published

Dec 4, 2025

Updated

Feb 22, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Feb 22, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

🦀libcrux-intrinsics🦀libcrux-ml-kem🦀libcrux-ml-dsa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libcrux-intrinsics`	≥ 0.0.3&&< 0.0.4	0.0.4`cargo update -p libcrux-intrinsics --precise 0.0.4`
🦀crates.io	`libcrux-ml-kem`	≥ 0.0.3&&< 0.0.4	0.0.4`cargo update -p libcrux-ml-kem --precise 0.0.4`
🦀crates.io	`libcrux-ml-dsa`	≥ 0.0.3&&< 0.0.4	0.0.4`cargo update -p libcrux-ml-dsa --precise 0.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-intrinsics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libcrux-intrinsics to 0.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cgv-28vr-rv6j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-2cgv-28vr-rv6j in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works