CVE-2026-54999

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows TCP/IP allows an unauthorized attacker to execute code over an adjacent network.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 14, 2026

Last Modified

September 17, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-54999

Vendor Advisories for CVE-2026-54999(2)

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 12× in last 7d / 96× 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 285 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54999?
CVE-2026-54999 is a high vulnerability published on July 14, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Windows TCP/IP allows an unauthorized attacker to execute code over an adjacent network.
When was CVE-2026-54999 disclosed?
CVE-2026-54999 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54999 actively exploited?
CVE-2026-54999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54999?
CVE-2026-54999 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54999, 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-54999

Explore →

Is Your Infrastructure Affected by CVE-2026-54999?

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