Signing-key disclosure via variable-time ML-DSA division
Published Jan 10, 2026 · Updated Jan 10, 2026
Timing side channel in RustCrypto Signatures before 0.1.0-rc.2 allows attackers to infer ML-DSA signing-key information. The ml-dsa decompose function divides secret-derived r1.0 by TwoGamma2::U32 with a hardware division whose runtime varies with operand values. Exploitation requires low-privileged adjacent access and sufficiently precise repeated timing measurements; the reported impact is signing-key information disclosure.
Summary
What happened
Timing side channel in RustCrypto Signatures before 0.1.0-rc.2 allows attackers to infer ML-DSA signing-key information. The ml-dsa decompose function divides secret-derived r1.0 by TwoGamma2::U32 with a hardware division whose runtime varies with operand values. Exploitation requires low-privileged adjacent access and sufficiently precise repeated timing measurements; the reported impact is signing-key information disclosure.
The record
- CVE
- CVE-2026-22705
- Published
- Jan 10, 2026
- Updated
- Jan 10, 2026
- Vendor
- RustCrypto
- Product
- Signatures
- Classifications
- CWE-1240
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 10, 2026CVE publishedPublication date reported by the CVE source.
- Jan 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.1.0-rc.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo