Authentication bypass by capture-replay in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.
CVE-2026-62911
Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. the CNA's CVSS baseline 8.0; sources differ by 0.0.
- 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.0
- EG Score
- 8.0(medium)
- EG Risk
- 52(Track*)EG Risk 52/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 computedSeverity80% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 1%
- EPSS %ILE
- 70%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
September 16, 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-62911Vendor Advisories for CVE-2026-62911(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 38× in last 7d / 197× 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 322 total refreshes for this CVE.
- 2026-09-19 14:40 UTCVendor advisory
- 2026-09-19 14:40 UTCGHSA enrichment
- 2026-09-19 01:57 UTCEG score recompute
- 2026-09-19 01:57 UTCVendor advisory
- 2026-09-19 01:57 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:09 UTCVendor advisory
- 2026-09-18 13:09 UTCGHSA enrichment
- 2026-09-18 00:37 UTCEG score recompute
- 2026-09-18 00:37 UTCVendor advisory
- 2026-09-18 00:37 UTCGHSA enrichment
- 2026-09-17 05:31 UTCVendor advisory
- 2026-09-17 05:31 UTCGHSA enrichment
- 2026-09-16 17:01 UTCEG score recompute
- 2026-09-16 17:01 UTCVendor advisory
- 2026-09-16 17:01 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 11:02 UTCEG score recompute
- 2026-09-16 11:02 UTCVendor advisory
- 2026-09-16 11:02 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 22:33 UTCVendor advisory
- 2026-09-15 22:32 UTCGHSA enrichment
- 2026-09-15 06:28 UTCEG score recompute
- 2026-09-15 06:28 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-15 06:28 UTCGHSA enrichment
- 2026-09-14 17:58 UTCVendor advisory
- 2026-09-14 17:58 UTCGHSA enrichment
- 2026-09-14 07:55 UTCVendor advisory
- 2026-09-14 07:55 UTCGHSA enrichment
- 2026-09-13 19:26 UTCEG score recompute
- 2026-09-13 19:26 UTCVendor advisory
- 2026-09-13 19:26 UTCGHSA enrichment
- 2026-09-13 06:56 UTCVendor advisory
- 2026-09-13 06:56 UTCGHSA enrichment
- 2026-09-12 18:15 UTCEG score recompute
- 2026-09-12 18:15 UTCVendor advisory
- 2026-09-12 18:15 UTCGHSA enrichment
- 2026-09-12 05:45 UTCVendor advisory
- 2026-09-12 05:45 UTCGHSA enrichment
- 2026-09-11 17:16 UTCVendor advisory
- 2026-09-11 17:16 UTCGHSA enrichment
- 2026-09-11 15:59 UTCVendor advisory
- 2026-09-11 15:59 UTCGHSA enrichment
- 2026-09-11 15:37 UTCEG score recompute
- 2026-09-11 15:37 UTCVendor advisory
- 2026-09-11 15:37 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-11 04:31 UTCEG score recompute
- 2026-09-11 04:31 UTCGHSA enrichment
- 2026-09-10 15:56 UTCEG score recompute
- 2026-09-10 15:56 UTCGHSA enrichment
- 2026-09-10 09:16 UTCGHSA enrichment
- 2026-09-09 20:28 UTCVendor advisory
- 2026-09-09 20:27 UTCGHSA enrichment
- 2026-09-09 10:40 UTCVendor advisory
- 2026-09-09 10:40 UTCGHSA enrichment
- 2026-09-08 22:10 UTCEG score recompute
- 2026-09-08 22:10 UTCVendor advisory
- 2026-09-08 22:09 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 18:21 UTCVendor advisory
- 2026-09-08 18:21 UTCGHSA enrichment
- 2026-09-08 07:13 UTCVendor advisory
- 2026-09-08 07:13 UTCGHSA enrichment
- 2026-09-07 18:41 UTCEG score recompute
- 2026-09-07 18:41 UTCVendor advisory
- 2026-09-07 18:41 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 06:12 UTCVendor advisory
- 2026-09-07 06:11 UTCGHSA enrichment
- 2026-09-06 15:27 UTCEG score recompute
- 2026-09-06 15:27 UTCVendor advisory
- 2026-09-06 15:27 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 02:56 UTCEG score recompute
- 2026-09-06 02:56 UTCVendor advisory
- 2026-09-06 02:56 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 14:26 UTCVendor advisory
- 2026-09-05 14:26 UTCGHSA enrichment
- 2026-09-05 01:27 UTCEG score recompute
- 2026-09-05 01:27 UTCVendor advisory
- 2026-09-05 01:27 UTCGHSA enrichment
- 2026-09-04 10:05 UTCEG score recompute
- 2026-09-04 10:05 UTCVendor advisory
- 2026-09-04 10:05 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 21:35 UTCVendor advisory
- 2026-09-03 21:35 UTCGHSA enrichment
- 2026-09-03 15:40 UTCVendor advisory
- 2026-09-03 15:40 UTCGHSA enrichment
- 2026-09-03 08:05 UTCVendor advisory
- 2026-09-03 08:05 UTCGHSA enrichment
- 2026-09-02 19:23 UTCVendor advisory
- 2026-09-02 19:23 UTCGHSA enrichment
- 2026-09-02 18:12 UTCGHSA enrichment
- 2026-09-02 17:40 UTCEG score recompute
- 2026-09-02 17:40 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoChypnguyen1209/CVE-2026-62911First seen Aug 22, 2026
POC pre-auth RCE on Exchange
Open source ↗
Frequently asked(5)
What is CVE-2026-62911?
When was CVE-2026-62911 disclosed?
Is CVE-2026-62911 actively exploited?
What is the CVSS score of CVE-2026-62911?
How do I remediate CVE-2026-62911?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62911
Is Your Infrastructure Affected by CVE-2026-62911?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.