CVE-2026-55007

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

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

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

Double free in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-55007

Vendor Advisories for CVE-2026-55007(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 49× in last 7d / 85× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55007?
CVE-2026-55007 is a high vulnerability published on September 8, 2026. Double free in Microsoft Exchange Server allows an unauthorized attacker to execute code over a network.
When was CVE-2026-55007 disclosed?
CVE-2026-55007 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55007 actively exploited?
CVE-2026-55007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.4% of all scored CVEs.
What is the CVSS score of CVE-2026-55007?
CVE-2026-55007 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-55007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55007, 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-55007

Explore →

Is Your Infrastructure Affected by CVE-2026-55007?

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

Start Free Scan →Browse All CVEs