PatchaPalooza

CVE-2026-33824: Windows Internet Key Exchange (IKE) Service Extensions Remote Code Execution Vulnerability

CVE-2026-33824 is a remote code execution vulnerability in Windows Internet Key Exchange (IKE) Service Extensions, rated Critical by Microsoft, with a CVSS 3.1 base score of 9.8 (Critical). An attacker can exploit it remotely over the network, without any privileges and without user interaction. Microsoft has not reported exploitation in the wild and rates exploitation as less likely. CISA added it to the Known Exploited Vulnerabilities catalog on 18 August 2026, with a remediation deadline of 21 August 2026 for US federal agencies. The EPSS model estimates a 77.05% probability of exploitation activity in the next 30 days, higher than 100% of all scored vulnerabilities. Microsoft released the fix on 14 April 2026 in the April 2026 Patch Tuesday, delivered through 9 security updates (KB5082123, KB5082142, KB5082200, KB5082063 and more). It affects 27 products in 2 product families (Windows, ESU).

Key facts

CVE ID
CVE-2026-33824
Severity
Critical CVSS 9.8
Microsoft severity
Critical
Impact
Remote Code Execution
Exploited in the wild
No
Publicly disclosed
No
Exploitation likelihood
Less Likely
Weakness
CWE-415
EPSS
77.05% (percentile 100%)
CISA KEV
Listed , due
Released
Last updated
Patch Tuesday
April 2026 Patch Tuesday
Product families
Windows, ESU

From the April 2026 Patch Tuesday briefing

Windows IKE Service Extensions Remote Code Execution

CISA KEV deadline: 2026-08-21. This is a remote code execution risk in Windows’ Internet Key Exchange (IKE) components, meaning an attacker could potentially run code on a target system over the network. The practical scenario is exploitation against systems that expose or rely on IKE/IPsec-related services, where a crafted network exchange could lead to system compromise without needing a user to click anything. With a Critical 9.8 score (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and a CWE-415 Double Free class, this is the month’s most dangerous “reach-and-run” condition: network-reachable, no authentication, no user interaction. In practical terms, any host exposing IKE/IPsec-related services (commonly UDP 500/4500) becomes a candidate for pre-auth remote code execution. Attackers would prioritize this for edge compromise, targeting VPN gateways, perimeter Windows servers, or misconfigured endpoints with exposed IKE, then immediately pivot to credential theft, persistence (service installation/scheduled tasks), and lateral movement.

From the briefing, written by an AI model from PatchaPalooza's data.

CVSS score and vector

Microsoft scores CVE-2026-33824 at 9.8 (temporal 8.5) using CVSS 3.1. Vector: 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

MetricValue
Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
Exploit code maturityUnproven
Remediation levelOfficial fix
Report confidenceConfirmed

Description

Double free in Windows IKE Extension allows an unauthorized attacker to execute code over a network.

Frequently asked questions (Microsoft)

How could an attacker exploit this vulnerability?

An unauthenticated attacker could send specially crafted packets to a Windows machine with Internet Key Exchange (IKE) version 2 enabled, which could enable remote code execution.

Mitigations and workarounds

The following mitigating factors might be helpful in your situation:

Customers who cannot immediately install the security update can take one of the following actions, depending on their environment:

  • Block inbound traffic on UDP ports 500 and 4500 for systems that do not use IKE.
  • For systems that require IKE, configure firewall rules to allow inbound traffic on UDP ports 500 and 4500 only from known peer addresses.

These actions reduce the attack surface but do not replace installing the security update

Affected products (27)

Windows

ProductSecurity updateTypeFixed buildRestart
Windows 10 Version 1809 for 32-bit SystemsKB5082123Security Update10.0.17763.8644Yes
Windows 10 Version 1809 for x64-based SystemsKB5082123Security Update10.0.17763.8644Yes
Windows Server 2019KB5082123Security Update10.0.17763.8644Yes
Windows Server 2019 (Server Core installation)KB5082123Security Update10.0.17763.8644Yes
Windows Server 2022KB5082142Security Update10.0.20348.5020Yes
Windows Server 2022 (Server Core installation)KB5082142Security Update10.0.20348.5020Yes
Windows 10 Version 21H2 for 32-bit SystemsKB5082200Security Update10.0.19044.7184Yes
Windows 10 Version 21H2 for ARM64-based SystemsKB5082200Security Update10.0.19044.7184Yes
Windows 10 Version 21H2 for x64-based SystemsKB5082200Security Update10.0.19044.7184Yes
Windows Server 2025 (Server Core installation)KB5082063Security Update10.0.26100.32690Yes
Windows 11 Version 25H2 for ARM64-based SystemsKB5083769Security Update10.0.26200.8246Yes
Windows 11 Version 25H2 for x64-based SystemsKB5083769Security Update10.0.26200.8246Yes
Windows 11 Version 23H2 for ARM64-based SystemsKB5082052Security Update10.0.22631.6936Yes
Windows 11 Version 23H2 for x64-based SystemsKB5082052Security Update10.0.22631.6936Yes
Windows Server 2022, 23H2 Edition (Server Core installation)KB5082060Security Update10.0.25398.2274Yes
Windows 11 Version 24H2 for ARM64-based Systems
Windows 11 Version 24H2 for x64-based Systems
Windows Server 2025KB5082063Security Update10.0.26100.32690Yes
Windows 11 version 26H1 for x64-based SystemsKB5083768Security Update10.0.28000.1836Yes
Windows 11 Version 26H1 for ARM64-based SystemsKB5083768Security Update10.0.28000.1836Yes
Windows 10 Version 1607 for 32-bit SystemsKB5082198Security Update10.0.14393.9060Yes
Windows 10 Version 1607 for x64-based SystemsKB5082198Security Update10.0.14393.9060Yes
Windows Server 2016KB5082198Security Update10.0.14393.9060Yes
Windows Server 2016 (Server Core installation)KB5082198Security Update10.0.14393.9060Yes

ESU

ProductSecurity updateTypeFixed buildRestart
Windows 10 Version 22H2 for x64-based Systems
Windows 10 Version 22H2 for ARM64-based Systems
Windows 10 Version 22H2 for 32-bit Systems

Security updates (9)

Exploitation and detection

CISA Known Exploited Vulnerabilities

Date added
Federal due date
Ransomware use
Unknown
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.

VulnCheck KEV

Date added
Ransomware use
Unknown
Independent sources
6

Detection and weaponization

Weaponization maturity: Exploit.

Proof-of-concept repositories (2)

NIST NVD data

NVD status
Analyzed
NVD CVSS
9.8 (CRITICAL)
NVD weakness
CWE-415
Published to NVD
NVD last modified

Affected configurations (CPE)

ProductVulnerable versions
windows 10 1607 (x64)before 10.0.14393.9060
windows 10 1607 (x86)before 10.0.14393.9060
windows 10 1809 (x64)before 10.0.17763.8644
windows 10 1809 (x86)before 10.0.17763.8644
windows 10 21h2 (arm64)before 10.0.19044.7184
windows 10 21h2 (x64)before 10.0.19044.7184
windows 10 21h2 (x86)before 10.0.19044.7184
windows 10 22h2 (arm64)before 10.0.19045.7184
windows 10 22h2 (x64)before 10.0.19045.7184
windows 10 22h2 (x86)before 10.0.19045.7184
windows 11 23h2 (arm64)before 10.0.22631.6936
windows 11 23h2 (x64)before 10.0.22631.6936
windows 11 24h2 (arm64)before 10.0.26100.8246
windows 11 24h2 (x64)before 10.0.26100.8246
windows 11 25h2 (arm64)before 10.0.26200.8246
windows 11 25h2 (x64)before 10.0.26200.8246
windows 11 26h1 (arm64)before 10.0.28000.1836
windows 11 26h1 (x64)before 10.0.28000.1836
windows server 2016before 10.0.14393.9060
windows server 2019before 10.0.17763.8644
windows server 2022before 10.0.20348.5020
windows server 2022 23h2before 10.0.25398.2274
windows server 2025before 10.0.26100.32690

References

Acknowledgments

  • WARP & MORSE team at Microsoft
  • WARP & MORSE team at Microsoft

Revision history

VersionDateDescription
1.0Information published.
1.1Added clarifying information to the mitigation. This is an informational change only.

Sources