RustCrypto signatures up to 0.1.0-rc.1 cryptographic primitive risky implementation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in RustCrypto signatures up to 0.1.0-rc.1. This affects an unknown part. The manipulation leads to cryptographic primitive risky implementation. This vulnerability is uniquely identified as CVE-2026-22705. The attack can only be initiated within the local network. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in RustCrypto signatures up to 0.1.0-rc.1. It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a cryptographic primitive risky implementation vulnerability. Using CWE to declare the problem leads to CWE-1240. To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-22705 since 01/08/2026. The exploitation is known to be difficult. The attack can only be done within the local network. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.1.0-rc.2 eliminates this vulnerability. Applying the patch 035d9eef98486ecd00a8bf418c7817eb14dd6558 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-1867). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cryptographic primitive risky implementationCWE: CWE-1240 / CWE-327 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: signatures 0.1.0-rc.2
Patch: 035d9eef98486ecd00a8bf418c7817eb14dd6558
Timeline
01/08/2026 CVE reserved01/10/2026 Advisory disclosed
01/10/2026 VulDB entry created
01/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-hcp2-x6j4-29j7
Status: Confirmed
CVE: CVE-2026-22705 (🔒)
GCVE (CVE): GCVE-0-2026-22705
GCVE (VulDB): GCVE-100-340397
EUVD: 🔒
Entry
Created: 01/10/2026 10:30Updated: 01/10/2026 23:43
Changes: 01/10/2026 10:30 (65), 01/10/2026 23:43 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.