CVE-2026-93599

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

rustls-webpki through 0.103.12 (and 0.104.0-alpha releases before 0.104.0-alpha.7) contains a reachable panic in bit_string_flags() in src/der.rs. The input guard fails to reject a named-bit BIT STRING whose content is exactly [0x00] (zero padding bits and no data bytes), so raw_bits.len() - 1 underflows on the empty slice and the subsequent index operation panics (subtract-with-overflow in debug, index-out-of-bounds in release). The condition is reachable through the public API BorrowedCertRevocationList::from_der() when a CRL contains an issuingDistributionPoint extension with such an onlySomeReasons value. Exploitation requires an application that explicitly opts in to CRL revocation checking by passing RevocationOptions to verify_for_usage() and that parses CRL bytes obtained from a source the attacker can influence; the default rustls configuration, which does not use RevocationOptions, is unaffected. A crafted CRL causes a denial of service via the panic. Fixed in 0.103.13 and 0.104.0-alpha.7.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

rustls-webpki before 0.103.13 Panic via empty BIT STRING | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rustls-webpki-before-0.103.13-panic-via-empty-bit-string
github Patch Available🟡 PoC Available

Panic in `BorrowedCertRevocationList::from_der` via empty `BIT STRING` in `IssuingDistributionPoint` · Advisory · rustls/webpki · GitHub

https://github.com/rustls/webpki/security/advisories/GHSA-82j2-j2ch-gfr8

Vendor Advisories for CVE-2026-93599(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 15:56 UTCEG score recompute
  2. 2026-09-19 15:55 UTCGHSA enrichment
  3. 2026-09-19 03:40 UTCEG score recompute
  4. 2026-09-19 03:40 UTCGHSA enrichment
  5. 2026-09-18 14:21 UTCEG score recompute
  6. 2026-09-18 13:29 UTCEG score recompute
  7. 2026-09-18 13:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93599?
CVE-2026-93599 is a high vulnerability published on September 18, 2026. rustls-webpki through 0.103.12 (and 0.104.0-alpha releases before 0.104.0-alpha.7) contains a reachable panic in bitstringflags() in src/der.rs. The input guard fails to reject a named-bit BIT STRING whose content is exactly [0x00] (zero padding bits and no data bytes), so rawbits.len() - 1…
When was CVE-2026-93599 disclosed?
CVE-2026-93599 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93599 actively exploited?
CVE-2026-93599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-93599?
CVE-2026-93599 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-93599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93599

Explore →

Is Your Infrastructure Affected by CVE-2026-93599?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.