sm2 Known Vulnerabilities & Fixes
sm2 has 3 known security vulnerabilities in crates.io (Rust). Review the table below for affected and fixed versions. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Is sm2 in your project?
Check if you're affected by these 3 vulnerabilities.
Security Summary
- 3 affected version ranges have been identified across these 3 advisories.
- 0% of known issues have a published fixed version.
- Remediation: cargo update -p sm2
Vulnerabilities
3 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Jan 9, 2026, most recently Jan 13, 2026 (4 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-22700 RustCrypto Has Insufficient Length Validation in decrypt() in SM2-PKE | HIGH | All versions | No fix available |
| CVE-2026-22699 SM2-PKE has Unchecked AffinePoint Decoding (unwrap) in decrypt() | HIGH | All versions | No fix available |
| CVE-2026-22698 SM2-PKE has 32-bit Biased Nonce Vulnerability | HIGH | All versions | No fix available |
About This Data
Vulnerability data for sm2 is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related crates.io (Rust) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of sm2.