Finding and attribution
Microsoft’s Patch Tuesday table identifies a TCP/IP flaw involving IPsec cross-SA fragment splicing during reassembly. The Microsoft CNA describes an authentication bypass that lets an authorized attacker bypass a security feature over a network; the sources do not provide a more detailed trigger.
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-35422.
AI and human contribution (source account): Microsoft’s May 12, 2026 article says its engineering teams found CVE-2026-35422 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 10 Version 1607 before 10.0.14393.9140, Windows 10 Version 1809 before 10.0.17763.8755, Windows 10 Version 21H2 before 10.0.19044.7291, Windows 10 Version 22H2 before 10.0.19045.7417, 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 2012 before 6.2.9200.26079, Windows Server 2012 (Server Core installation) before 6.2.9200.26079, Windows Server 2012 R2 before 6.3.9600.23181, Windows Server 2012 R2 (Server Core installation) before 6.3.9600.23181, Windows Server 2016 before 10.0.14393.9140, Windows Server 2016 (Server Core installation) before 10.0.14393.9140, Windows Server 2019 before 10.0.17763.8755, Windows Server 2019 (Server Core installation) before 10.0.17763.8755, Windows Server 2022 before 10.0.20348.5139, 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: Medium · highest recorded score 6.5. Documented technical effects: authentication bypass.
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-35422: CVSS 3.1 · 6.5 (Medium) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C. Microsoft CNA CVE record · checked 17 Nov 2026.
CVE-2026-35422: authentication bypass.
Prerequisites / affected scope: An authorized attacker can exploit the network-reachable TCP/IP condition; the Microsoft blog identifies IPsec cross-SA fragment splicing during reassembly. No further trigger or downstream consequence is asserted..
Exploitation evidence: The sources describe a bypass scenario and 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.9140, Windows 10 Version 1809 before 10.0.17763.8755, Windows 10 Version 21H2 before 10.0.19044.7291, Windows 10 Version 22H2 before 10.0.19045.7417, 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 2012 before 6.2.9200.26079, Windows Server 2012 (Server Core installation) before 6.2.9200.26079, Windows Server 2012 R2 before 6.3.9600.23181, Windows Server 2012 R2 (Server Core installation) before 6.3.9600.23181, Windows Server 2016 before 10.0.14393.9140, Windows Server 2016 (Server Core installation) before 10.0.14393.9140, Windows Server 2019 before 10.0.17763.8755, Windows Server 2019 (Server Core installation) before 10.0.17763.8755, Windows Server 2022 before 10.0.20348.5139, 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.