Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

Windows SMB Server Elevation of Privilege via Kerberos Reflection

IdentifiersCVE-2026-26128CWE-287· Improper Authentication

CVE-2026-26128 is an elevation-of-privilege vulnerability in Windows SMB Server caused by improper authentication. Based on the provided content, the issue is tied to a Kerberos reflection technique derived from research into bypassing prior fixes for SMB/Kerberos coercion. The attack abuses Unicode normalization discrepancies in Windows and Active Directory to coerce a machine account into requesting a Kerberos service ticket for a crafted hostname that still maps to the real machine account SPN, then relays the resulting Kerberos AP-REQ back to the local SMB service from a local IP address. Microsoft assigned CVE-2026-26128 after researchers adapted a previously demonstrated authenticated remote code execution path into a local privilege escalation scenario that satisfies newer SMB loopback checks. Successful exploitation results in the SMB service accepting reflected authentication and granting execution context as NT AUTHORITY\SYSTEM.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authorized attacker to elevate privileges to NT AUTHORITY\SYSTEM on the affected Windows host. The content indicates this is effectively a local privilege escalation path in patched environments, though Microsoft also describes it as allowing an authorized attacker to elevate privileges over a network. In practical terms, compromise of a lower-privileged context can be converted into full local system control, enabling complete takeover of the host, access to protected resources, credential theft, persistence, and follow-on lateral movement.

Mitigation

If you can’t patch tonight, do this now.

Ensure SMB signing for loopback connections is enforced. The content states the RequireSecuritySignatureForLoopback registry value at HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters\RequireSecuritySignatureForLoopback defaults to 1, and setting it to 0 reintroduces SMB reflection vulnerabilities. Windows 11 24H2 is noted as not vulnerable to the default SMB reflection path because SMB signing is enforced. As a defensive measure, do not disable this setting, restrict opportunities for local coercion and relay, and monitor for anomalous Kerberos authentication involving crafted Unicode hostnames and SMB loopback/reflection behavior.

Remediation

Patch, then assume compromise.

Apply Microsoft's March 2026 Patch Tuesday security update for CVE-2026-26128. The provided content states Microsoft patched the issue in March 2026 and that the final SMB fix added logic in srv2!Smb2ExecuteNegotiateReal to require signing for loopback connections when RequireSecuritySignatureForLoopback is enabled. Organizations should ensure the relevant Windows SMB Server updates are installed across affected systems and verify that SMB signing protections for loopback connections remain enabled.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-26128MaturityPoCVerified exploit

This repository is a standalone Python exploit for CVE-2026-26128, described as Kerberos reflection via a Unicode SPN bypass in Windows Active Directory. The main entry point is CVE-2026-26128.py, which orchestrates the full attack chain: parse operator credentials and target parameters, derive a crafted Unicode hostname from the chosen target, add that hostname as an AD-integrated DNS A record via LDAP, wait for propagation, start a local SMB relay server on port 445, and then trigger coerced authentication from the victim/DC using either PetitPotam (EFSRPC) or DFSCoerce (DFSNM). When the coerced Kerberos authentication reaches the attacker SMB listener, the code extracts the AP-REQ/SPN and relays it to a configured target service. Repository structure is modular. lib/dns contains LDAP-based ADIDNS management used to add/remove the malicious DNS record. lib/coerce contains the coercion primitives: petitpotam.py triggers EFSRPC-based UNC access to \\<listener>\test\Settings.ini, and dfscoerce.py triggers DFSNM-based coercion over \\PIPE\netdfs. lib/servers contains the relay listeners, especially smbrelayserver.py, which implements the SMB listener and includes Unicode normalization logic to match the relayed SPN hostname back to the intended target. httprelayserver.py provides HTTP/WebDAV relay handling. lib/clients contains protocol relay clients for HTTP/HTTPS and MSSQL. The HTTP client relays Kerberos to web targets such as AD CS Web Enrollment; the MSSQL client performs Kerberos-authenticated TDS login and supports execution of operator-supplied SQL queries through ntlmrelayx attack plumbing. lib/utils contains configuration and Kerberos/SPNEGO parsing helpers. Primary exploit capability is Kerberos relay enabled by a Unicode hostname confusion trick: the tool registers a Unicode lookalike DNS name that resolves to the attacker, causing the target/DC to request a service ticket and connect to the attacker-controlled SMB service. The SMB relay server then forwards the Kerberos authentication to a chosen target. For AD CS targets, the expected result is issuance of a machine certificate saved as a .pfx file, after which the tool prints a gettgtpkinit.py command to obtain a TGT via PKINIT. For MSSQL targets, the exploit can authenticate and run arbitrary SQL queries provided with -q/--query. This is clearly exploit code rather than a detector, and it is operational because it contains end-to-end attack logic and usable payload actions, though payload customization is relatively basic and not embedded in a larger exploitation framework.

jarnovandenbrinkDisclosed May 5, 2026pythonmarkdownnetworkweb
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
Microsoft CorporationWindows Smb Serveroperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.