AI Science Tracker

Windows DNS heap buffer overflow permits remote code execution

Windows DNS Client · AI involvement attributed to Microsoft Security multi-model agentic scanning harness (MDASH; individual model assignments not identified)

Finding and attribution

Microsoft identifies a heap-based buffer overflow in Windows DNS, triggered by a crafted UDP DNS response, and classifies it as remote code execution. The CNA states that an unauthorized attacker can execute code over a network.

Product: Windows DNS Client. 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-41096.

AI and human contribution (source account): Microsoft’s May 12, 2026 article says its engineering teams found CVE-2026-41096 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-05-12; 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 11 version 23H2 before 10.0.22631.7079, Windows 11 Version 23H2 before 10.0.22631.7219, Windows 11 Version 24H2 before 10.0.26100.8457, Windows 11 Version 25H2 before 10.0.26200.8457, Windows 11 version 26H1 before 10.0.28000.2113, Windows Server 2022, 23H2 Edition (Server Core installation) before 10.0.25398.2330, Windows Server 2025 before 10.0.26100.32860, Windows Server 2025 (Server Core installation) before 10.0.26100.32860. 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 12 May 2026. AI attribution dated 12 May 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.8. 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-41096: CVSS 3.1 · 9.8 (Critical) · CVSS:3.1/AV:N/AC:L/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-41096: code execution.
Prerequisites / affected scope: Microsoft’s table identifies a crafted UDP DNS response; the CNA describes an unauthorized attacker reaching Windows DNS over a network. No additional environment conditions are stated..
Exploitation evidence: No exploitation in the wild is reported in the cited sources.. Impact source · checked 17 Nov 2026.

Documented fix: Microsoft’s CNA lists product-specific affected builds and fixed cutoffs: Windows 11 version 23H2 before 10.0.22631.7079, Windows 11 Version 23H2 before 10.0.22631.7219, Windows 11 Version 24H2 before 10.0.26100.8457, Windows 11 Version 25H2 before 10.0.26200.8457, Windows 11 version 26H1 before 10.0.28000.2113, Windows Server 2022, 23H2 Edition (Server Core installation) before 10.0.25398.2330, Windows Server 2025 before 10.0.26100.32860, Windows Server 2025 (Server Core installation) before 10.0.26100.32860. These are build-specific Microsoft patch boundaries, not an assertion of installed patch status.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases