Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote sender crash software that uses affected RustCrypto SM2 public-key decryption. The issue is limited to prerelease/RC versions 0.14.0-pre.0 and 0.14.0-rc.0 of RustCrypto elliptic-curves. Business impact is service disruption, not data theft or tampering, based on the published CVSS and advisory details.
Executive priority
Prioritize if your organization uses Rust-based cryptography services with SM2 decryption exposed to untrusted clients. For most organizations, urgency depends on whether these prerelease/RC library versions are present. The main business risk is outage or degraded availability.
Technical view
In the SM2 PKE decrypt() path, invalid C1 elliptic-curve coordinates can decode to None/CtOption::None. A prior unchecked unwrap() causes a panic instead of rejecting the invalid point. The CVE maps to CWE-20 and has CVSS 7.5: network, low complexity, no privileges, no user interaction, availability impact only. The issue is patched by commit 085b7be.
Likely exposure
Exposure is likely only where applications depend on RustCrypto elliptic-curves 0.14.0-pre.0 or 0.14.0-rc.0 and process untrusted SM2 PKE ciphertexts. Stable versions are not listed as affected in the provided sources.
Exploitation context
The advisory describes a denial-of-service panic reachable through malformed SM2 ciphertext input. CISA KEV is false in the provided bundle, and no cited source reports active exploitation. Treat externally reachable decryption services as higher priority because CVSS indicates network access and no authentication are required.
Researcher notes
The source bundle identifies a specific unchecked unwrap in SM2 PKE decrypt(), fixed by GitHub PR 1602 and commit 085b7be. Evidence does not name a released fixed version. Avoid assuming broader RustCrypto or non-SM2 impact without confirming dependency use and code path reachability.
Mitigation direction
- Identify use of RustCrypto elliptic-curves 0.14.0-pre.0 or 0.14.0-rc.0.
- Move off affected prerelease/RC versions or apply the patched commit when appropriate.
- Check the GitHub advisory and project guidance for the supported fixed release path.
- Prioritize internet-facing services that decrypt SM2 PKE data from untrusted sources.
Validation and detection
- Review dependency manifests and lockfiles for elliptic-curves affected versions.
- Confirm whether the application uses SM2 PKE decryption functionality.
- Verify deployed builds include the fix from commit 085b7be or later vendor guidance.
- Monitor crash logs for panic patterns during SM2 decryption error handling.
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-20: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22699 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/RustCrypto/elliptic-curves/security/advisories/GHSA-78p6-6878-8mj6CVE reference · x_refsource_CONFIRM
- https://github.com/RustCrypto/elliptic-curves/pull/1602CVE reference · x_refsource_MISC
- https://github.com/RustCrypto/elliptic-curves/commit/085b7bee647029bd189e1375203418205006bcabCVE 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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.