Finding and attribution
Microsoft reports a race-driven use-after-free in the Windows IPv4 receive path: Ipv4pReceiveRoutingHeader releases its Path reference and later reuses the pointer while handling Strict Source and Record Route (SSRR) packets. Microsoft says remote unauthenticated SSRR packets can reach the path and describe a narrow timing window and allocator-reuse preconditions. Microsoft classifies the CVE as remote code execution, while its deep dive describes controlled reads and potential stronger corruption rather than reporting observed exploitation.
Product: Windows TCP/IP. AI system: Microsoft Security multi-model agentic scanning harness (MDASH; individual model assignments not identified). Team / organization: Microsoft Autonomous Code Security / MORSE / WARP.
CVE identifiers: CVE-2026-33827.
AI and human contribution (source account): Microsoft’s May 12, 2026 article says its engineering teams found CVE-2026-33827 using codename MDASH and lists the CVE in the cohort. Microsoft describes MDASH as a multi-model agentic pipeline with specialized auditor, validation/debate, deduplication and proof stages. The article does not identify the particular model/agent contribution for this finding.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Microsoft’s CNA record dates public disclosure 2026-04-14; the AI-attribution article was published 2026-05-12. For CVE-2026-33824 and CVE-2026-33827, Microsoft says they were patched in April Patch Tuesday even though the cases appear in the May 12 article. The cited sources do not report exploitation in the wild.
Remediation status: fix documented. Microsoft’s CNA lists product-specific affected builds and fixed cutoffs: Windows 10 Version 1607 before 10.0.14393.9060, Windows 10 Version 1809 before 10.0.17763.8644, Windows 10 Version 21H2 before 10.0.19044.7184, Windows 10 Version 22H2 before 10.0.19045.7184, Windows 11 version 23H2 before 10.0.22631.6936, Windows 11 Version 23H2 before 10.0.22631.6936, Windows 11 Version 24H2 before 10.0.26100.8246, Windows 11 Version 25H2 before 10.0.26200.8246, Windows 11 version 26H1 before 10.0.28000.1836, Windows Server 2012 before 6.2.9200.26026, Windows Server 2012 (Server Core installation) before 6.2.9200.26026, Windows Server 2012 R2 before 6.3.9600.23132, Windows Server 2012 R2 (Server Core installation) before 6.3.9600.23132, Windows Server 2016 before 10.0.14393.9060, Windows Server 2016 (Server Core installation) before 10.0.14393.9060, Windows Server 2019 before 10.0.17763.8644, Windows Server 2019 (Server Core installation) before 10.0.17763.8644, Windows Server 2022 before 10.0.20348.5020, Windows Server 2022, 23H2 Edition (Server Core installation) before 10.0.25398.2274, Windows Server 2025 before 10.0.26100.32690, Windows Server 2025 (Server Core installation) before 10.0.26100.32690. These are build-specific Microsoft patch boundaries, not an assertion of installed patch status.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 14 Apr 2026. AI attribution dated 12 May 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.1. Documented technical effects: code execution.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-33827: CVSS 3.1 · 8.1 (High) ·
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C. Microsoft CNA CVE record · checked 17 Nov 2026.
CVE-2026-33827: code execution.
Prerequisites / affected scope: Microsoft’s deep dive says an attacker sends crafted IPv4 packets with the SSRR option, reaches the path under standard validation, and wins a narrow timing window while allocator reuse occurs. The Microsoft table classifies the issue as RCE; the deep dive describes potential controlled reads and a stronger corruption primitive if the allocation is attacker-influenced..
Exploitation evidence: MSRC describes exploitability conditions; the cited sources do not report exploitation in the wild.. Impact source · checked 17 Nov 2026.
Documented fix: Microsoft’s CNA lists product-specific affected builds and fixed cutoffs: Windows 10 Version 1607 before 10.0.14393.9060, Windows 10 Version 1809 before 10.0.17763.8644, Windows 10 Version 21H2 before 10.0.19044.7184, Windows 10 Version 22H2 before 10.0.19045.7184, Windows 11 version 23H2 before 10.0.22631.6936, Windows 11 Version 23H2 before 10.0.22631.6936, Windows 11 Version 24H2 before 10.0.26100.8246, Windows 11 Version 25H2 before 10.0.26200.8246, Windows 11 version 26H1 before 10.0.28000.1836, Windows Server 2012 before 6.2.9200.26026, Windows Server 2012 (Server Core installation) before 6.2.9200.26026, Windows Server 2012 R2 before 6.3.9600.23132, Windows Server 2012 R2 (Server Core installation) before 6.3.9600.23132, Windows Server 2016 before 10.0.14393.9060, Windows Server 2016 (Server Core installation) before 10.0.14393.9060, Windows Server 2019 before 10.0.17763.8644, Windows Server 2019 (Server Core installation) before 10.0.17763.8644, Windows Server 2022 before 10.0.20348.5020, Windows Server 2022, 23H2 Edition (Server Core installation) before 10.0.25398.2274, Windows Server 2025 before 10.0.26100.32690, Windows Server 2025 (Server Core installation) before 10.0.26100.32690. These are build-specific Microsoft patch boundaries, not an assertion of installed patch status.