Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighPublic exploit

Windows SMB Server Elevation of Privilege via NTLM Reflection Bypass

IdentifiersCVE-2026-24294CWE-287· Improper Authentication

CVE-2026-24294 is an elevation-of-privilege vulnerability in Windows SMB Server caused by improper authentication. Available reporting indicates it is an NTLM reflection bypass that abuses a feature introduced in Windows 11 24H2 and Windows Server 2025 allowing SMB connections over arbitrary TCP ports. An attacker can start a local SMB server on a non-standard port, establish a client connection to it using the arbitrary-port SMB capability, and then coerce a privileged local service such as LSASS running as NT AUTHORITY\SYSTEM to access the same SMB path. Because the Windows SMB client reuses the existing TCP connection and SMB supports multiplexed authenticated sessions over one connection, the privileged NTLM authentication can be captured on the attacker-controlled local SMB listener and relayed back to the host's real SMB service. Successful relay yields a SYSTEM-authenticated SMB session on the same machine. Microsoft patched the issue in March 2026 Patch Tuesday. Reporting states the exploit works by default on Windows Server 2025, while Windows 11 24H2 is not vulnerable by default because SMB signing is enforced.

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 a local authorized attacker to elevate privileges to NT AUTHORITY\SYSTEM on the affected host. This results in full local compromise, including the ability to execute code with SYSTEM privileges, access or modify protected data, tamper with security controls, establish persistence, and use the host for further post-exploitation activity.

Mitigation

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

If immediate patching is not possible, enforce SMB signing to block the relay path, reduce or disable NTLM where operationally feasible, and monitor for anomalous SMB activity involving localhost or non-standard TCP ports. Investigate use of arbitrary-port SMB mounts, unexpected local SMB listeners, suspicious net use commands with /tcpport, and coercion activity consistent with PetitPotam-style primitives. Restricting local attacker execution opportunities also reduces exposure, since the attack requires code execution on the target host.

Remediation

Patch, then assume compromise.

Apply Microsoft's March 2026 security updates that address CVE-2026-24294. Prioritize patching Windows Server 2025 systems, as reporting indicates the issue is exploitable by default there. Validate that SMB signing policies remain enforced after patching and review any configurations that permit or rely on SMB over non-standard TCP ports.
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-24294MaturityPoCVerified exploit

Repository contains a working exploit chain combining a modified Windows PetitPotam coercion client with a modified Impacket SMB server. The purpose is local NTLM reflection / privilege escalation on Windows Server 2025 by abusing SMB arbitrary-port connections plus SMB session multiplexing. The C++ project under PetitPotam/ is a Visual Studio solution that binds to the EFSRPC interface UUID df1941c5-fe89-4e79-bf10-463657acf44d over the named pipe \\pipe\\efsrpc using ncacn_np. It accepts three arguments: capture server, target server, and EFS API selector. It constructs a UNC path to \\<captureServer>\test\topotam.exe and invokes one of several EFSRPC methods (notably EfsRpcEncryptFileSrv in the README example) against the target. Success is inferred from expected RPC error codes such as ERROR_BAD_NETPATH or ERROR_ACCESS_DENIED, indicating the target attempted outbound access to the attacker-controlled UNC path. The generated files ms-efsrpc_c.c, ms-efsrpc_h.h, ms-dtyp.h, and ms-dtyp_h.h are MIDL-generated RPC client stubs and type definitions supporting the EFSRPC calls. They are not standalone exploit logic but provide the RPC interface implementation used by PetitPotam.cpp. The Python smbserver.py is a modified Impacket SMB server entry point. It adds a -relay-port option and hooks SMB2 SESSION_SETUP handling to capture a second NTLM authentication on an already-established multiplexed SMB connection, then forwards that authentication to a raw relay listener such as ntlmrelayx --raw-port. This turns the coerced authentication into a usable relay/reflection primitive. The README documents the full three-terminal workflow: start ntlmrelayx on raw port 6666 targeting smb://127.0.0.1, start smbserver.py on TCP 12345 with share name test and relay-port 6666, then mount \\127.0.0.1\test using /tcpport:12345 and run PetitPotam.exe 127.0.0.1 localhost 2. Expected outcome is command execution as NT AUTHORITY\SYSTEM. Overall, this is a real exploit repository, not merely detection code. It is operational rather than heavily weaponized: the coercion path/share is partly hardcoded, the workflow is manual, and it relies on external tooling (Impacket ntlmrelayx) for final command execution.

0xNDIDisclosed Apr 30, 2026cppclocalnetworkweb
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 malware6

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

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 activity11

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