Critical [CVE-2026-33824] Windows Internet Key Exchange (IKE) Service Extensions Remote Code Execution Vulnerability
This critical-severity Microsoft Server advisory covers CVE-2026-33824 affecting Windows Server 2016 (Server Core installation), Windows Server 2019 (Server Core installation), Windows Server 2022, 23H2 Edition (Server Core installation).
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Microsoft Server CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Double free in Windows IKE Extension allows an unauthorized attacker to execute code over a network.
Affected products named by the advisory: Windows Server 2016; Windows Server 2016 (Server Core installation); Windows Server 2019; Windows Server 2019 (Server Core installation); and 4 more.
Affected products named by the advisory: Windows Server 2022, 23H2 Edition (Server Core installation); Windows Server 2025 (Server Core installation).
CISA Known Exploited Vulnerability
- Listed:
- Aug 18, 2026 · federal remediation due Aug 21, 2026
- Required action:
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Ransomware use:
- Unknown
KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.
- Windows 10 Version 1607 10.0.14393.0 before 10.0.14393.9060
- Windows 10 Version 1809 10.0.17763.0 before 10.0.17763.8644
- Windows 10 Version 21H2 10.0.19044.0 before 10.0.19044.7184
- Windows 10 Version 22H2 10.0.19045.0 before 10.0.19045.7184
- Windows 11 version 22H3 10.0.22631.0 before 10.0.22631.6936
- Windows 11 Version 23H2 10.0.22631.0 before 10.0.22631.6936
- Windows 11 Version 24H2 10.0.26100.0 before 10.0.26100.8246
- Windows 11 Version 25H2 10.0.26200.0 before 10.0.26200.8246
- Windows 11 version 26H1 10.0.28000.0 before 10.0.28000.1836
- Windows Server 2016 10.0.14393.0 before 10.0.14393.9060
- Windows Server 2016 (Server Core installation) 10.0.14393.0 before 10.0.14393.9060
- Windows Server 2019 10.0.17763.0 before 10.0.17763.8644
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
- 10.0.14393.9060
- 10.0.17763.8644
- 10.0.19044.7184
- 10.0.19045.7184
- 10.0.22631.6936
- 10.0.26100.8246
- 10.0.26200.8246
- 10.0.28000.1836
- 10.0.20348.5020
- 10.0.25398.2274
- 10.0.26100.32690
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation
Upgrade to a fixed release: 10.0.14393.9060, 10.0.17763.8644, 10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 10.0.26100.8246. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.