CVE-2026-55145

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.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: 7.1Exploit: None knownExposed: 0

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

Improper neutralization of special elements used in a command ('command injection') in Outlook Copilot allows an authorized attacker to perform tampering over a network.

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

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jul 15, 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-55145

Vendor Advisories for CVE-2026-55145(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 34× in last 7d / 166× 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 232 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55145?
CVE-2026-55145 is a high vulnerability published on July 14, 2026. Improper neutralization of special elements used in a command ('command injection') in Outlook Copilot allows an authorized attacker to perform tampering over a network.
When was CVE-2026-55145 disclosed?
CVE-2026-55145 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55145 actively exploited?
CVE-2026-55145 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 57.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55145?
CVE-2026-55145 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-55145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55145, 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-55145

Explore →

Is Your Infrastructure Affected by CVE-2026-55145?

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