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

Windows TCP/IP Remote Code Execution Vulnerability

IdentifiersCVE-2026-33827CWE-362· Concurrent Execution using Shared…

CVE-2026-33827 is a Critical remote code execution vulnerability in the Windows TCP/IP stack (tcpip.sys). The issue is described as concurrent execution using a shared resource with improper synchronization, i.e., a race condition, and multiple supporting sources further characterize it as involving a use-after-free condition in tcpip.sys. Public reporting in the provided content states the flaw can be triggered remotely by sending specially crafted IPv6 packets to a Windows node with IPSec enabled; some references also mention crafted packets involving IPv4 Strict Source and Record Route processing, but the most consistently repeated exploitation condition in the supplied material is IPv6 with IPSec enabled. Successful exploitation requires the attacker to win the race condition and prepare the target environment appropriately, after which code execution may be achieved over the network without authentication or user interaction.

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 remote code execution on the affected Windows system from a network position. The attacker does not need authentication and no user interaction is required. Because the flaw is in the Windows TCP/IP stack, exploitation could provide a highly valuable pre-authentication foothold on exposed systems and may be wormable in some configurations discussed in the supplied reporting, particularly where IPv6 and IPSec are enabled.

Mitigation

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

No specific vendor workaround is provided in the supplied content beyond patching. Until updates can be applied, reduce exposure by limiting untrusted network access to affected hosts, especially systems where IPv6 and IPSec are enabled. More generally, minimizing external reachability of vulnerable Windows nodes may reduce attack surface while remediation is in progress.

Remediation

Patch, then assume compromise.

Apply Microsoft's official security update for CVE-2026-33827 to all affected and supported Windows systems. Use the Microsoft Security Update Guide and product lifecycle guidance to identify the correct patches for each affected version. Prioritize systems with exposed network services and configurations where IPv6 and IPSec are 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-33827MaturityPoCVerified exploit

Repository is very small and consists of a long README plus a single Python PoC script. The README describes an alleged Windows TCP/IP IPv6/IPSec race-condition RCE, CVE-2026-33827, affecting Windows 10/11/Server and requiring network reachability plus IPSec. It includes defensive guidance, references, and high-level exploitation theory, but no concrete exploit internals beyond pseudocode. The actual code in exploit.py is a Scapy-based packet generator. It defines a placeholder target IPv6 address (fe80::...) and interface (eth0), builds an Ethernet frame carrying an IPv6 packet with a Destination Options header, an IPv6 Fragment header with randomized fragment ID, and a 1200-byte raw payload of repeated 'X' characters. The flood() function then repeatedly transmits this packet at Layer 2 using sendp(..., loop=1, inter=0), effectively creating a continuous malformed/fragmented IPv6 packet flood. Main exploit capability: network-based packet crafting and flooding intended to stress or trigger the claimed vulnerable Windows IPv6/IPSec processing path. The script does not implement IPSec negotiation, race orchestration across threads/processes, memory corruption primitives, shellcode delivery, callback infrastructure, or any reliable RCE chain. As such, this is best characterized as a proof-of-concept traffic generator rather than a complete weaponized exploit. Repository structure and purpose: README serves as vulnerability overview and remediation guidance; exploit.py is the only executable component and the likely entry point. Overall purpose appears to be demonstrating how to generate suspicious IPv6 fragmented traffic against a Windows target, not delivering a full end-to-end compromise.

kaleth4Disclosed Apr 22, 2026markdownpythonnetworkwireless
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 CorporationWindowsoperating_system
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

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 activity11

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