CVE-2026-15418

LOWPre-NVD 2.42.4
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.4Exploit: None knownExposed: 0

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

In the silabser.sys driver for CP210x devices v11.5.0 and earlier, a local unprivileged user with a malicious device can use malformed packets to leak up to 145 bytes of uninitialized kernel pool memory. This vulnerability affects Windows 10 and earlier.

CVSS v3
2.4
EG Score
2.4(medium)
EG Risk
11(Track)
EG Risk 11/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
Severity24% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 10, 2026

Vendor Advisories for CVE-2026-15418(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 9× in last 7d / 16× 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-18 19:27 UTCEPSS rescore
  2. 2026-09-17 06:05 UTCEG score recompute
  3. 2026-09-17 06:05 UTCGHSA enrichment
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:14 UTCEPSS rescore
  6. 2026-09-14 01:01 UTCEG score recompute
  7. 2026-09-14 01:01 UTCGHSA enrichment
  8. 2026-09-13 16:46 UTCEPSS rescore
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-10 19:58 UTCGHSA enrichment
  12. 2026-09-10 19:19 UTCEG score recompute
  13. 2026-09-10 19:19 UTCGHSA enrichment
  14. 2026-09-10 18:22 UTCEG score recompute
  15. 2026-09-10 17:25 UTCEG score recompute
  16. 2026-09-10 17:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15418?
CVE-2026-15418 is a low vulnerability published on September 10, 2026. In the silabser.sys driver for CP210x devices v11.5.0 and earlier, a local unprivileged user with a malicious device can use malformed packets to leak up to 145 bytes of uninitialized kernel pool memory. This vulnerability affects Windows 10 and earlier.
When was CVE-2026-15418 disclosed?
CVE-2026-15418 was first published in the National Vulnerability Database on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15418 actively exploited?
CVE-2026-15418 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 95.0% of all scored CVEs.
What is the CVSS score of CVE-2026-15418?
CVE-2026-15418 has a CVSS v3 base score of 2.4 (NVD).
How do I remediate CVE-2026-15418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15418, 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-15418

Explore →

Is Your Infrastructure Affected by CVE-2026-15418?

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