CVE-2026-62910

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 49% 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
8.8EG
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.8Exploit: None knownExposed: 0

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

Improper control of resource identifiers ('resource injection') in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a 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%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-62910

Vendor Advisories for CVE-2026-62910(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 33× in last 7d / 180× 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 294 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-62910?
CVE-2026-62910 is a high vulnerability published on August 11, 2026. Improper control of resource identifiers ('resource injection') in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.
When was CVE-2026-62910 disclosed?
CVE-2026-62910 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62910 actively exploited?
CVE-2026-62910 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 49.2% of all scored CVEs.
What is the CVSS score of CVE-2026-62910?
CVE-2026-62910 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62910?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62910, 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-62910

Explore →

Is Your Infrastructure Affected by CVE-2026-62910?

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