Improper authentication in Windows SMB Server allows an authorized attacker to elevate privileges locally.
CVE-2026-26128
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-10. the CNA's CVSS baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 51(Track)EG Risk 51/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 computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 47%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 19, 2026
Advisory Details (3)
Auto-updated Jun 10, 2026CVE-2026-26128 Mitigation Script - Improper Authentication in Windows SMB Server - vsociety
https://www.vicarius.io/vsociety/posts/cve-2026-26128-mitigation-script-improper-authentication-in-windows-smb-serverCVE-2026-26128 Detection Script - Improper Authentication in Windows SMB Server - vsociety
https://www.vicarius.io/vsociety/posts/cve-2026-26128-detection-script-improper-authentication-in-windows-smb-serverSecurity Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26128Vendor Advisories for CVE-2026-26128(2)
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 6× in last 7d / 54× 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.
Showing the most recent 100 of 193 total refreshes for this CVE.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:07 UTCEG score recompute
- 2026-08-16 12:07 UTCVendor advisory
- 2026-08-16 12:07 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 20:40 UTCVendor advisory
- 2026-08-14 20:40 UTCGHSA enrichment
- 2026-08-14 08:03 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-14 08:03 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:28 UTCEG score recompute
- 2026-08-12 23:28 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 22:00 UTCEG score recompute
- 2026-08-11 22:00 UTCVendor advisory
- 2026-08-11 22:00 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 05:08 UTCEG score recompute
- 2026-08-11 05:08 UTCVendor advisory
- 2026-08-11 05:08 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:57 UTCVendor advisory
- 2026-08-10 08:57 UTCGHSA enrichment
- 2026-08-09 20:20 UTCEG score recompute
- 2026-08-09 20:20 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 07:44 UTCEG score recompute
- 2026-08-09 07:44 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 07:42 UTCVendor advisory
- 2026-08-08 07:42 UTCGHSA enrichment
- 2026-08-07 19:05 UTCEG score recompute
- 2026-08-07 19:05 UTCGHSA enrichment
- 2026-08-06 20:05 UTCEG score recompute
- 2026-08-06 20:05 UTCVendor advisory
- 2026-08-06 20:05 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:13 UTCEG score recompute
- 2026-08-06 02:13 UTCVendor advisory
- 2026-08-06 02:12 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 01:38 UTCEG score recompute
- 2026-08-04 01:38 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 17:56 UTCEG score recompute
- 2026-08-02 17:56 UTCVendor advisory
- 2026-08-02 17:56 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:07 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCjarnovandenbrink/CVE-2026-26128First seen May 5, 2026
PoC for exploiting CVE-2026-26128.
Open source ↗
Frequently asked(5)
What is CVE-2026-26128?
When was CVE-2026-26128 disclosed?
Is CVE-2026-26128 actively exploited?
What is the CVSS score of CVE-2026-26128?
How do I remediate CVE-2026-26128?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26128
Is Your Infrastructure Affected by CVE-2026-26128?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.