# GHSA-2cgv-28vr-rv6j: libcrux incorrectly calculates on aarch64

> Incorrect SHA-3 and post-quantum crypto calculations on aarch64 lead to invalid signatures and shared secrets, compromising cryptographic integrity.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2025
- **Also known as:** RUSTSEC-2025-0133

## What is GHSA-2cgv-28vr-rv6j?

GHSA-2cgv-28vr-rv6j is a vulnerability in libcrux-intrinsics, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

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

7 open source packages ship an affected version, including libcrux-intrinsics, libcrux-ml-dsa and libcrux-ml-kem.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcrux-intrinsics` | crates.io | From 0.0.3 | 0.0.4 |
| `libcrux-intrinsics` | crates.io | From 0.0.3 | 0.0.4 |
| `libcrux-intrinsics` | crates.io | From 0.0.4-0 | 0.0.4 |
| `libcrux-ml-dsa` | crates.io | From 0.0.3 | 0.0.4 |
| `libcrux-ml-dsa` | crates.io | From 0.0.3 | 0.0.4 |
| `libcrux-ml-kem` | crates.io | From 0.0.3 | 0.0.4 |
| `libcrux-ml-kem` | crates.io | From 0.0.3 | 0.0.4 |

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

Upgrade libcrux-intrinsics to 0.0.4 or later.

## Is GHSA-2cgv-28vr-rv6j being exploited?

There is no known exploitation of GHSA-2cgv-28vr-rv6j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2cgv-28vr-rv6j and fix it if it is affected.

What it is: GHSA-2cgv-28vr-rv6j is a vulnerability in libcrux-intrinsics, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2cgv-28vr-rv6j in the wild and no public exploit code.

Affected packages and fixed versions:
- libcrux-intrinsics (crates.io): affected from 0.0.3; fixed in 0.0.4
- libcrux-intrinsics (crates.io): affected from 0.0.3; fixed in 0.0.4
- libcrux-intrinsics (crates.io): affected from 0.0.4-0; fixed in 0.0.4
- libcrux-ml-dsa (crates.io): affected from 0.0.3; fixed in 0.0.4
- libcrux-ml-dsa (crates.io): affected from 0.0.3; fixed in 0.0.4
- libcrux-ml-kem (crates.io): affected from 0.0.3; fixed in 0.0.4
- libcrux-ml-kem (crates.io): affected from 0.0.3; fixed in 0.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2cgv-28vr-rv6j/ (Markdown: https://insights.sbomify.com/GHSA-2cgv-28vr-rv6j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2cgv-28vr-rv6j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2cgv-28vr-rv6j/
Summaries are generated and may contain mistakes; the official description above is the record.