CVE-2026-26128
vulnerability analysis and mitigation

Overview

CVE-2026-26128 is an improper authentication vulnerability in the Windows SMB Server that allows a locally authenticated attacker with low privileges to elevate their privileges on the affected system. Disclosed on March 10, 2026, as part of Microsoft's Patch Tuesday, it affects a broad range of Windows versions including Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1), Windows Server 2012/2012 R2, 2016, 2019, 2022, 2022 23H2, and 2025. It carries a CVSS v3.1 base score of 7.8 (High) (Microsoft MSRC).

Technical details

The vulnerability is rooted in improper authentication (CWE-287) within the Windows SMB Server component, where authentication logic can be abused or bypassed by a locally authenticated attacker. The attack vector is local, requires low privileges, no user interaction, and has low attack complexity, making it straightforward to exploit once an attacker has a foothold on the system. Related attack patterns include authentication bypass (CAPEC-115), token impersonation (CAPEC-633), and access token manipulation (T1134), suggesting the flaw may involve improper handling of authentication tokens or session credentials within the SMB stack. A public proof-of-concept has been published at https://github.com/jarnovandenbrink/CVE-2026-26128, and a technical write-up by Synacktiv on bypassing Windows authentication reflection mitigations provides additional context (Synacktiv, Microsoft MSRC).

Impact

Successful exploitation allows an attacker with low-level local access to escalate privileges to SYSTEM level, achieving complete compromise of the affected Windows host. This enables arbitrary code execution with the highest available permissions, potentially leading to credential harvesting, malware installation, data exfiltration, and lateral movement within the network. All three security pillars — confidentiality, integrity, and availability — are rated HIGH impact (Microsoft MSRC).

Exploitation steps

  1. Gain Local Access: Obtain a low-privileged local user account on a vulnerable Windows system (e.g., via phishing, credential stuffing, or exploitation of another vulnerability).
  2. Reconnaissance: Confirm the target is running an unpatched Windows version (e.g., Windows 10 22H2 before 10.0.19045.7058, Windows 11 24H2 before 10.0.26100.7979, or Windows Server 2022 before 10.0.20348.4830) by checking the OS build number.
  3. Exploit SMB Authentication Flaw: Leverage the improper authentication weakness in the Windows SMB Server — potentially through authentication reflection or token impersonation techniques — to bypass privilege checks. The public PoC at https://github.com/jarnovandenbrink/CVE-2026-26128 provides a starting point.
  4. Achieve SYSTEM Privileges: The exploit results in code execution or token manipulation at SYSTEM level, granting full control over the local machine.
  5. Post-Exploitation: Use SYSTEM-level access to dump credentials (e.g., via LSASS), install persistence mechanisms, or pivot laterally to other systems on the network (Synacktiv).

Indicators of compromise

  • Logs: Unusual SMB authentication events in the Windows Security Event Log (Event IDs 4624, 4672) showing privilege escalation from low-privileged accounts; unexpected SYSTEM-level logon sessions originating from non-administrative users.
  • Process: Unexpected processes spawned with SYSTEM privileges from user-context processes; unusual child processes of svchost.exe or SMB-related services (e.g., lsass.exe access from non-standard processes).
  • Network: Anomalous SMB traffic (port 445) from internal hosts, particularly authentication negotiation sequences that deviate from normal patterns.
  • File System: New files or scheduled tasks created under SYSTEM context by non-administrative user sessions; unexpected modifications to sensitive system directories.
  • Registry: New autorun entries or service registrations created under SYSTEM context following a low-privileged user session.

Mitigation and workarounds

Microsoft released patches on March 10, 2026, addressing this vulnerability across all affected platforms. Administrators should update to the following minimum build versions: Windows 10 1607/Server 2016 → 10.0.14393.8957; Windows 10 1809/Server 2019 → 10.0.17763.8511; Windows 10 21H2 → 10.0.19044.7058; Windows 10 22H2 → 10.0.19045.7058; Windows 11 23H2 → 10.0.22631.6783; Windows 11 24H2 → 10.0.26100.7979; Windows 11 25H2 → 10.0.26200.7979; Windows 11 26H1 → 10.0.28000.1719; Windows Server 2022 → 10.0.20348.4830; Windows Server 2022 23H2 → 10.0.25398.2207; Windows Server 2025 → 10.0.26100.32463. As interim mitigations, restrict local access to trusted users only, monitor SMB Server authentication logs for anomalies, and apply the principle of least privilege to limit the blast radius of any exploitation (Microsoft MSRC).

Community reactions

The vulnerability was covered as part of broader March 2026 Patch Tuesday roundups by multiple security vendors and researchers. Rapid7, Talos Intelligence, Zero Day Initiative, and Sophos all included it in their monthly patch analysis, noting it as a notable privilege escalation affecting a wide range of Windows versions. The CVE appeared in Reddit's CVEWatch trending lists for early May 2026 following the publication of the public PoC, indicating growing community interest. Synacktiv published a technical blog post on bypassing Windows authentication reflection mitigations that provides relevant context for this class of vulnerability (Synacktiv, ZDI Blog, Rapid7 Blog).

Additional resources


SourceThis report was generated using AI

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management