CVE-2026-41089

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Stack-based buffer overflow in Windows Netlogon allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
61st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Oct 20, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-41089(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 25× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 483 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 383 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (6 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCSyntaxMethod/CVE-2026-41089-Netlogon-RCE-PoC
    Published Sep 11, 2026

    CVE-2026-41089 Netlogon RCE PoC — security research, vulnerability validation & defensive testing.

    Open source ↗
  • GitHub PoCZeroDayVPN/CVE-2026-41089-Netlogon
    Published Sep 10, 2026

    🛡️ Official AI Security Tool diagnostic module for CVE-2026-41089 (Windows Netlogon Stack Buffer Overflow RCE). Features technical writeup, attack architecture, IoCs, and mitigation strategy.

    Open source ↗
  • GitHub PoCHydraSoft/CVE-2026-41089-Netlogon-RCE
    Published Jul 21, 2026

    Technical analysis and Proof-of-Concept (PoC) for CVE-2026-41089, a critical unauthenticated Remote Code Execution (RCE) vulnerability in the Windows Netlogon service affecting Domain Controllers.

    Open source ↗
  • GitHub checkerADScanPro/CVE-2026-41089-LongLogon
    Published Jun 3, 2026

    CVE-2026-41089 checker: unauthenticated, non-destructive detection for the Netlogon CLDAP stack buffer overflow (CVSS 9.8). Reports whether a domain controller's domain is long enough to crash, without sending the overflow. The binary-verified analysis the public PoCs got wrong.

    Open source ↗
  • GitHub PoChnytgl/CVE-2026-41089
    Published Jun 3, 2026

    CVE-2026-41089 - Windows Netlogon CLDAP Remote Code Execution Exploit (CVSS 9.8)

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-41089
    Published Jun 2, 2026

    CVE-2026-41089

    Open source ↗
  • GitHub PoC0xABCD01/CVE-2026-41089
    Published Jun 1, 2026

    CVE-2026-41089 PoC — Netlogon CLDAP stack buffer overflow (CVSS 9.8 CRITICAL)

    Open source ↗

Frequently asked(5)

What is CVE-2026-41089?
CVE-2026-41089 is a critical-severity vulnerability; its CVE record was published on May 12, 2026. Stack-based buffer overflow in Windows Netlogon allows an unauthorized attacker to execute code over a network.
When was CVE-2026-41089 made public?
CVE-2026-41089 was made public on May 12, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on May 12, 2026. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-41089 actively exploited?
CVE-2026-41089 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41089?
CVE-2026-41089 has a CVSS base score of 9.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-41089?
A fix for CVE-2026-41089 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41089 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41089?

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