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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: Elevated riskExposed: 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 PROB
2%
EPSS %ILE
79%
KEV
Not listed

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 31, 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 6× in last 7d / 127× 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 469 total refreshes for this CVE.

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

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 ↗

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 August 10, 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 2% probability of exploitation in the next 30 days, which ranks it in the top 21.3% of all scored CVEs.
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