Security readout for executives and security teams
Plain-English summary
CVE-2026-22700 is a denial-of-service flaw in RustCrypto elliptic-curves SM2 encryption code. If an application accepts attacker-controlled SM2 ciphertext, malformed short inputs can trigger a Rust panic and crash the calling thread or process. The issue affects only versions 0.14.0-pre.0 and 0.14.0-rc.0.
Executive priority
Prioritize remediation for internet-facing or untrusted-input services using RustCrypto SM2-PKE on the affected pre-release versions. The business risk is service disruption, not data theft or privilege escalation based on current sources. If the affected versions are not present, urgency is low.
Technical view
In RustCrypto elliptic-curves 0.14.0-pre.0 and 0.14.0-rc.0, SM2-PKE decrypt() performs unchecked slice::split_at operations on untrusted ciphertext-derived buffers. Undersized ciphertext or crafted DER structures can cause bounds-check panics. The CVE maps to CWE-20 and carries CVSS 3.1 7.5, network exploitable with availability impact only.
Likely exposure
Exposure is likely limited to Rust applications using the affected pre-release or release-candidate elliptic-curves versions and invoking SM2-PKE decrypt() on untrusted input. Applications not using SM2-PKE decrypt(), or not using these specific versions, are not indicated as affected by the provided sources.
Exploitation context
The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. Exploitation requires reaching an application path that passes attacker-controlled malformed SM2 ciphertext or DER-encoded data into decrypt(). Impact is denial of service through panic-induced thread or process crash.
Researcher notes
The vulnerability is rooted in insufficient length validation before split_at on ciphertext-derived buffers. Patch review should focus on added bounds checks for SM2-PKE ciphertext and DER handling. Evidence is limited to the CVE/advisory, PR, and patch commit; no public exploitation evidence is provided.
Mitigation direction
- Identify use of RustCrypto elliptic-curves 0.14.0-pre.0 or 0.14.0-rc.0.
- Apply the vendor patch commit e60e991 or a vendor-recommended fixed release when available.
- Avoid exposing SM2-PKE decrypt() to untrusted ciphertext until patched.
- Monitor the GitHub advisory for updated remediation guidance.
Validation and detection
- Review Cargo.lock and dependency manifests for affected elliptic-curves versions.
- Confirm whether application code or dependencies call SM2-PKE decrypt().
- Check deployed builds include commit e60e991 or later vendor guidance.
- Review crash logs for Rust panics in SM2 decrypt processing.
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-22700 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-j9xq-69pf-pcm8CVE reference · x_refsource_CONFIRM
- https://github.com/RustCrypto/elliptic-curves/pull/1603CVE reference · x_refsource_MISC
- https://github.com/RustCrypto/elliptic-curves/commit/e60e99167a9a2b187ebe80c994c5204b0fdaf4abCVE 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.