CVE-2026-41096

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Heap-based buffer overflow in Microsoft Windows DNS allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
77.9%
KEV
Not listed

Published

May 12, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jul 12, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41096

Vendor Advisories for CVE-2026-41096(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 301 total refreshes for this CVE.

  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:17 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:11 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-08 15:15 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 75 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-28 14:07 UTCEPSS rescore
  8. 2026-06-28 12:59 UTCVendor advisory
  9. 2026-06-28 12:59 UTCGHSA enrichment
  10. 2026-06-28 08:22 UTCVendor advisory
  11. 2026-06-28 08:22 UTCGHSA enrichment
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-28 01:48 UTCVendor advisory
  14. 2026-06-28 01:48 UTCGHSA enrichment
  15. 2026-06-27 13:14 UTCVendor advisory
  16. 2026-06-27 13:14 UTCGHSA enrichment
  17. 2026-06-27 08:20 UTCVendor advisory
  18. 2026-06-27 08:20 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-26 20:45 UTCVendor advisory
  21. 2026-06-26 20:45 UTCGHSA enrichment
  22. 2026-06-26 04:01 UTCVendor advisory
  23. 2026-06-26 04:01 UTCGHSA enrichment
  24. 2026-06-25 21:17 UTCVendor advisory
  25. 2026-06-25 21:17 UTCGHSA enrichment
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-23 21:33 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-17 22:48 UTCVendor advisory
  39. 2026-06-17 22:48 UTCGHSA enrichment
  40. 2026-06-17 17:53 UTCEPSS rescore
  41. 2026-06-17 03:24 UTCGHSA enrichment
  42. 2026-06-16 23:35 UTCGHSA enrichment
  43. 2026-06-16 17:52 UTCEPSS rescore
  44. 2026-06-16 11:35 UTCVendor advisory
  45. 2026-06-16 11:35 UTCGHSA enrichment
  46. 2026-06-16 05:34 UTCVendor advisory
  47. 2026-06-16 05:34 UTCGHSA enrichment
  48. 2026-06-15 17:49 UTCEPSS rescore
  49. 2026-06-15 05:59 UTCVendor advisory
  50. 2026-06-15 05:59 UTCGHSA enrichment
  51. 2026-06-15 02:09 UTCVendor advisory
  52. 2026-06-15 02:09 UTCGHSA enrichment
  53. 2026-06-14 22:21 UTCVendor advisory
  54. 2026-06-14 22:21 UTCGHSA enrichment
  55. 2026-06-14 18:28 UTCVendor advisory
  56. 2026-06-14 18:28 UTCGHSA enrichment
  57. 2026-06-14 14:23 UTCVendor advisory
  58. 2026-06-14 14:22 UTCGHSA enrichment
  59. 2026-06-14 10:26 UTCVendor advisory
  60. 2026-06-14 10:26 UTCGHSA enrichment
  61. 2026-06-14 06:28 UTCVendor advisory
  62. 2026-06-14 06:28 UTCGHSA enrichment
  63. 2026-06-14 00:42 UTCVendor advisory
  64. 2026-06-14 00:42 UTCGHSA enrichment
  65. 2026-06-13 23:00 UTCEPSS rescore
  66. 2026-06-13 08:55 UTCVendor advisory
  67. 2026-06-13 08:55 UTCGHSA enrichment
  68. 2026-06-13 05:06 UTCVendor advisory
  69. 2026-06-13 05:06 UTCGHSA enrichment
  70. 2026-06-13 00:29 UTCVendor advisory
  71. 2026-06-13 00:29 UTCGHSA enrichment
  72. 2026-06-12 23:12 UTCEPSS rescore
  73. 2026-06-12 23:12 UTCEPSS rescore
  74. 2026-06-12 20:40 UTCVendor advisory
  75. 2026-06-12 20:40 UTCGHSA enrichment

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCTwoSevenOneT/CVE-2026-41096-Attack-Surface
    First seen Jun 4, 2026

    Attack surface in the real-world environment of CVE-2026-41096

    Open source ↗
  • GitHub PoCsatchfunky/CVE-2026-41096-POC
    First seen May 24, 2026

    windows api bug

    Open source ↗
  • GitHub PoCm0n1x90/CVE-2026-41096
    First seen May 24, 2026

    CVE-2026-41096: Heap Overflow in the Windows DNS Client

    Open source ↗
  • GitHub PoCmrk336/DNS-Mayhem-CVE-2026-41096-Deep-Dive
    First seen May 15, 2026

    In‑depth technical analysis of CVE‑2026‑41096, a critical heap overflow in Windows DNSAPI.dll enabling remote code execution via crafted DNS responses. Includes attack vectors, patch insights, and defensive guidance for security teams.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41096?
CVE-2026-41096 is a critical vulnerability published on May 12, 2026. Heap-based buffer overflow in Microsoft Windows DNS allows an unauthorized attacker to execute code over a network.
When was CVE-2026-41096 disclosed?
CVE-2026-41096 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41096 actively exploited?
CVE-2026-41096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41096?
CVE-2026-41096 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41096?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41096, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41096

Explore →

Is Your Infrastructure Affected by CVE-2026-41096?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs