# CVE-2026-22705: RustCrypto: Signatures has timing side-channel in ML-DSA decomposition

> A timing side-channel in the ML-DSA decomposition algorithm allows attackers to potentially recover private keys from RustCrypto Signatures users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-hcp2-x6j4-29j7, RUSTSEC-2025-0144

## What is CVE-2026-22705?

CVE-2026-22705 is a medium-severity vulnerability in RustCrypto signatures, published on 10 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RustCrypto: Signatures offers support for digital signatures, which provide authentication of data using public-key cryptography. Prior to version 0.1.0-rc.2, a timing side-channel was discovered in the Decompose algorithm which is used during ML-DSA signing to generate hints for the signature. This issue has been patched in version 0.1.0-rc.2.

Weakness: CWE-1240 (Use of a Cryptographic Primitive with a Risky Implementation)

## Which versions are affected by CVE-2026-22705?

3 open source packages ship an affected version, including ml-dsa.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ml-dsa` | crates.io | All versions | 0.1.0-rc.3 |
| `ml-dsa` | crates.io | All versions | 0.1.0-rc.3 |
| `ml-dsa` | crates.io | From 0.0.0-0 | 0.1.0-rc.3 |

## How do I fix CVE-2026-22705?

Upgrade ml-dsa to 0.1.0-rc.3 or later.

## Is CVE-2026-22705 being exploited?

There is no known exploitation of CVE-2026-22705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22705 and fix it if it is affected.

What it is: CVE-2026-22705 is a medium-severity vulnerability in RustCrypto signatures, published on 10 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22705 in the wild and no public exploit code.

Affected packages and fixed versions:
- ml-dsa (crates.io): affected all versions; fixed in 0.1.0-rc.3
- ml-dsa (crates.io): affected all versions; fixed in 0.1.0-rc.3
- ml-dsa (crates.io): affected from 0.0.0-0; fixed in 0.1.0-rc.3

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/CVE-2026-22705/ (Markdown: https://insights.sbomify.com/CVE-2026-22705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22705
- OSV: https://osv.dev/vulnerability/CVE-2026-22705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22705/
Summaries are generated and may contain mistakes; the official description above is the record.