Security readout for executives and security teams
Plain-English summary
CVE-2026-22705 affects RustCrypto’s signatures library before 0.1.0-rc.2. A timing side channel in ML-DSA signing could leak sensitive information under difficult conditions. This matters most for systems using this Rust library for post-quantum ML-DSA signatures. The issue is patched in 0.1.0-rc.2.
Executive priority
Treat as a targeted cryptographic library update, not an internet-wide emergency. Prioritize products or services using RustCrypto signatures for ML-DSA signing, especially in sensitive authentication or signing workflows. Patch during the next security update cycle unless exposure is confirmed in critical systems.
Technical view
The flaw is a CWE-1240 timing side channel in the Decompose algorithm used during ML-DSA signing hint generation. The CVSS 3.1 score is 6.4 with high attack complexity, low privileges required, no user interaction, and high confidentiality and integrity impact. Affected versions are RustCrypto signatures prior to 0.1.0-rc.2.
Likely exposure
Exposure is limited to applications or services that depend on RustCrypto signatures versions below 0.1.0-rc.2 and use ML-DSA signing functionality. Organizations not using this library, or not using ML-DSA signing paths, are not indicated as affected by the provided sources.
Exploitation context
The source bundle does not show known active exploitation, and the CVE is not marked KEV. The CVSS vector indicates adjacent attack vector, high complexity, and low privileges. Practical risk depends on an attacker’s ability to observe timing behavior around ML-DSA signing operations.
Researcher notes
Available sources identify the vulnerable algorithm, affected version range, CVSS vector, and patch version. They do not provide evidence of exploitation, detailed attack prerequisites, or affected downstream products. Avoid assuming broader RustCrypto impact beyond the signatures crate and ML-DSA signing path.
Mitigation direction
- Upgrade RustCrypto signatures to version 0.1.0-rc.2 or later.
- Identify applications using RustCrypto signatures before 0.1.0-rc.2.
- Prioritize systems performing ML-DSA signing operations.
- Review RustCrypto’s advisory and patch references for implementation details.
- If key exposure is suspected, follow internal cryptographic key incident procedures.
Validation and detection
- Check dependency manifests and lockfiles for RustCrypto signatures versions below 0.1.0-rc.2.
- Confirm whether affected applications use ML-DSA signing functionality.
- Verify builds resolve to patched version 0.1.0-rc.2 or later.
- Review software composition analysis results for transitive dependency exposure.
- Document systems where ML-DSA signing is externally reachable or multi-tenant.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1240: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22705 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N1.25.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/RustCrypto/signatures/security/advisories/GHSA-hcp2-x6j4-29j7CVE reference · x_refsource_CONFIRM
- https://github.com/RustCrypto/signatures/pull/1144CVE reference · x_refsource_MISC
- https://github.com/RustCrypto/signatures/commit/035d9eef98486ecd00a8bf418c7817eb14dd6558CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Cryptographic Primitive with a Risky Implementation
Use of a Cryptographic Primitive with a Risky Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.