cve.bz

CVE-2026-62911 microsoft: Authentication Bypass by Capture-replay

8.0 highEPSS 0.7%Fix available

High (8.0) in microsoft. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Authentication bypass by capture-replay in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-294 Authentication Bypass by Capture-replay
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-62911 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62911?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62911?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62911 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-62911

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-62911](https://cve.bz/cve/badge/CVE-2026-62911.svg)](https://cve.bz/cve/CVE-2026-62911)

HTML:

<a href="https://cve.bz/cve/CVE-2026-62911"><img src="https://cve.bz/cve/badge/CVE-2026-62911.svg" alt="CVE-2026-62911"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Exchange Server 2016 Cumulative Update 23from 15.01.0.0 before 15.01.2507.072
Microsoft Exchange Server 2019 Cumulative Update 14from 15.02.0.0 before 15.02.1544.044
Microsoft Exchange Server 2019 Cumulative Update 15from 15.02.0.0 before 15.02.1748.049
Microsoft Exchange Server Subscription Edition RTMfrom 15.02.0.0 before 15.02.2562.046

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Microsoft Exchange Server MRSProxy Initial WCF Handshake (CVE-2026-62911) sid 2071833
  • Emerging Threats Open ET EXPLOIT Microsoft Exchange Server MRSProxy Trigger File Write via PSTSession.Open() (CVE-2026-62911) sid 2071834

Attack patterns (CAPEC)

  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High
  • CAPEC-509 Kerberoasting Severity: High
  • CAPEC-555 Remote Services with Stolen Credentials Severity: Very High
  • CAPEC-561 Windows Admin Shares with Stolen Credentials
  • CAPEC-644 Use of Captured Hashes (Pass The Hash) Likelihood: Medium · Severity: High
  • CAPEC-645 Use of Captured Tickets (Pass The Ticket) Likelihood: Low · Severity: High
  • CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
  • CAPEC-701 Browser in the Middle (BiTM) Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON