Improper control of resource identifiers ('resource injection') in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.
CVE-2026-62910
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity88% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 20, 2026
Advisory Details (1)
Auto-updated Aug 11, 2026Security 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-62910Vendor 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 80× in last 7d / 125× 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 125 total refreshes for this CVE.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:01 UTCVendor advisory
- 2026-08-20 22:01 UTCGHSA enrichment
- 2026-08-20 16:43 UTCVendor advisory
- 2026-08-20 16:43 UTCGHSA enrichment
- 2026-08-20 15:01 UTCVendor advisory
- 2026-08-20 15:01 UTCGHSA enrichment
- 2026-08-20 14:13 UTCVendor advisory
- 2026-08-20 14:13 UTCGHSA enrichment
- 2026-08-20 09:50 UTCVendor advisory
- 2026-08-20 09:50 UTCGHSA enrichment
- 2026-08-19 21:15 UTCVendor advisory
- 2026-08-19 21:15 UTCGHSA enrichment
- 2026-08-19 17:46 UTCEG score recompute
- 2026-08-19 17:46 UTCVendor advisory
- 2026-08-19 17:46 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:51 UTCVendor advisory
- 2026-08-19 16:51 UTCGHSA enrichment
- 2026-08-19 15:15 UTCVendor advisory
- 2026-08-19 15:15 UTCGHSA enrichment
- 2026-08-19 14:31 UTCVendor advisory
- 2026-08-19 14:31 UTCGHSA enrichment
- 2026-08-19 11:20 UTCVendor advisory
- 2026-08-19 11:20 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-18 22:44 UTCGHSA enrichment
- 2026-08-18 22:13 UTCVendor advisory
- 2026-08-18 22:13 UTCGHSA enrichment
- 2026-08-18 17:28 UTCVendor advisory
- 2026-08-18 17:28 UTCGHSA enrichment
- 2026-08-18 13:56 UTCEG score recompute
- 2026-08-18 13:56 UTCVendor advisory
- 2026-08-18 13:55 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 06:54 UTCGHSA enrichment
- 2026-08-17 18:19 UTCVendor advisory
- 2026-08-17 18:19 UTCGHSA enrichment
- 2026-08-17 16:19 UTCEG score recompute
- 2026-08-17 16:19 UTCVendor advisory
- 2026-08-17 16:19 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:32 UTCVendor advisory
- 2026-08-17 07:32 UTCGHSA enrichment
- 2026-08-16 18:57 UTCVendor advisory
- 2026-08-16 18:57 UTCGHSA enrichment
- 2026-08-16 18:45 UTCVendor advisory
- 2026-08-16 18:45 UTCGHSA enrichment
- 2026-08-16 17:35 UTCVendor advisory
- 2026-08-16 17:35 UTCGHSA enrichment
- 2026-08-16 16:38 UTCEG score recompute
- 2026-08-16 16:38 UTCVendor advisory
- 2026-08-16 16:38 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:47 UTCEG score recompute
- 2026-08-16 11:47 UTCVendor advisory
- 2026-08-16 11:47 UTCGHSA enrichment
- 2026-08-15 23:13 UTCVendor advisory
- 2026-08-15 23:13 UTCGHSA enrichment
- 2026-08-15 10:38 UTCEG score recompute
- 2026-08-15 10:38 UTCVendor advisory
- 2026-08-15 10:38 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:02 UTCVendor advisory
- 2026-08-14 22:02 UTCGHSA enrichment
- 2026-08-14 21:18 UTCVendor advisory
- 2026-08-14 21:18 UTCGHSA enrichment
- 2026-08-14 20:27 UTCVendor advisory
- 2026-08-14 20:27 UTCGHSA enrichment
- 2026-08-14 18:38 UTCVendor advisory
- 2026-08-14 18:38 UTCGHSA enrichment
- 2026-08-14 17:35 UTCVendor advisory
- 2026-08-14 17:35 UTCGHSA enrichment
- 2026-08-14 17:09 UTCVendor advisory
- 2026-08-14 17:09 UTCGHSA enrichment
- 2026-08-14 16:28 UTCVendor advisory
- 2026-08-14 16:28 UTCGHSA enrichment
- 2026-08-14 15:30 UTCEG score recompute▲ 1.60
- 2026-08-14 15:30 UTCVendor advisory
- 2026-08-14 15:30 UTCGHSA enrichment
- 2026-08-14 15:29 UTCNVD updateCVSS v3 → 8.8
- 2026-08-14 06:10 UTCEG score recompute
- 2026-08-14 06:10 UTCVendor advisory
- 2026-08-14 06:10 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:35 UTCVendor advisory
- 2026-08-13 17:35 UTCGHSA enrichment
- 2026-08-13 16:32 UTCVendor advisory
- 2026-08-13 16:32 UTCGHSA enrichment
- 2026-08-13 06:53 UTCVendor advisory
- 2026-08-13 06:52 UTCGHSA enrichment
- 2026-08-12 18:15 UTCVendor advisory
- 2026-08-12 18:15 UTCGHSA enrichment
- 2026-08-12 15:21 UTCEG score recompute
- 2026-08-12 15:21 UTCVendor advisory
- 2026-08-12 15:21 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 05:34 UTCEG score recompute
- 2026-08-12 05:34 UTCVendor advisory
- 2026-08-12 05:34 UTCGHSA enrichment
- 2026-08-12 04:25 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-62910?
When was CVE-2026-62910 disclosed?
Is CVE-2026-62910 actively exploited?
What is the CVSS score of CVE-2026-62910?
How do I remediate CVE-2026-62910?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62910
Is Your Infrastructure Affected by CVE-2026-62910?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.