# CVE-2026-33824: Microsoft Internet Key Exchange (IKE) Service Extensions Double Free

> An unauthorized attacker can execute code over the network via a double free vulnerability in the Windows IKE Service Extensions.

- **Severity:** Critical 9.8 (`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`)
- **Exploited in the wild:** Yes, since 18 Aug 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-q6qf-3m2m-xq4f

## What is CVE-2026-33824?

CVE-2026-33824 is a critical use after free vulnerability in Microsoft Windows 10 1607, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2026-33824?

It affects 13 products.


Products: Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2026-33824?

No fix has been published for CVE-2026-33824 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Aug 2026.

## Is CVE-2026-33824 being exploited?

Yes. Attackers have exploited CVE-2026-33824 in the wild since at least 18 Aug 2026.

Public exploit code:

- IKEv2, ikeext.dll, CVE-2026-33824, double free, heap grooming, ROP, SKF fragmentation, Windows exploit, anti-debug, obfuscation, API hooking, shellcode, reverse shell (github_poc): https://github.com/EpSiLoNPoInTOrI/IKEV2-POC
- https://github.com/kaleth4/CVE-2026-33824 (github_poc): https://github.com/kaleth4/CVE-2026-33824

## Other vulnerabilities in Microsoft Windows 10 1607

- [CVE-2026-21510](https://insights.sbomify.com/CVE-2026-21510/): Microsoft Windows Shell Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2026-21513](https://insights.sbomify.com/CVE-2026-21513/): Microsoft MSHTML Framework Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2023-32049](https://insights.sbomify.com/CVE-2023-32049/): Microsoft Windows Defender SmartScreen Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2023-29360](https://insights.sbomify.com/CVE-2023-29360/): Microsoft Streaming Service Untrusted Pointer Dereference (high 8.4, exploited in the wild)
- [CVE-2026-85880](https://insights.sbomify.com/CVE-2026-85880/): Microsoft Windows Heap-Based Buffer Overflow (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33824 and fix it if it is affected.

What it is: CVE-2026-33824 is a critical use after free vulnerability in Microsoft Windows 10 1607, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-33824 in the wild since at least 18 Aug 2026.

Affected product: Microsoft Windows 10 1607. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33824/ (Markdown: https://insights.sbomify.com/CVE-2026-33824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33824
- OSV: https://osv.dev/vulnerability/CVE-2026-33824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33824/
Summaries are generated and may contain mistakes; the official description above is the record.