cve.bz

CVE-2026-26179 microsoft: Double Free

7.8 highEPSS 0.5%

High (7.8) in microsoft. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Double free in Windows Kernel allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-415 Double Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-26179 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-26179?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-26179?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-26179 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-26179

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-26179](https://cve.bz/cve/badge/CVE-2026-26179.svg)](https://cve.bz/cve/CVE-2026-26179)

HTML:

<a href="https://cve.bz/cve/CVE-2026-26179"><img src="https://cve.bz/cve/badge/CVE-2026-26179.svg" alt="CVE-2026-26179"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.6936
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.6936
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.8246
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.8246
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.1836
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.2274
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.32690
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.32690

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • nikosecurity/CVE-2026-26179 Harbor Check: matches CVE 1 star, C, created
    PoC for CVE-2026-26179 / ZDI-26-276, my very own Secure Kernel bug

References

Check your stackJSON