Microsoft Exchange Server Elevation of Privilege Vulnerability
Not confirmed exploited. 1 of 8 rule sources name it. 1 public exploit repo.
Authentication bypass by capture-replay in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable over the network, with low privileges and user interaction, leading to full loss of confidentiality, integrity and availability.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityNo special conditions are needed; the attack works reliably.Low
- Privileges requiredThe attacker needs an ordinary user account.Low
- User interactionA user has to do something first, such as open a file or click a link.Required
- ScopeThe damage stays within the vulnerable component.Unchanged
- Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impactAn attacker can change any data or files the affected component protects.High
- Availability impactAn attacker can take the component down completely or keep it from serving anyone.High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CAlso in the vector: Exploit code maturity: Unproven · Remediation level: Official fix · Report confidence: Confirmed
Public exploit code or a detailed write-up exists, but CISA has not seen attacks.
At least one step needs hands-on work, which slows mass attacks.
A successful attack gives full control over the affected software or all of its data.
Public exploits
1 foundNo exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2026-08-11CVE publishedCVE List
- 2026-10-21F5 ships a ruleMicrosoft Exchange MRSProxy Authentication Bypass
- 2026-11-02First public exploit repositoryc5z54/cve-2026-62911-poc: CVE-2026-62911 — Exchange MRSProxy Pre-Auth RCE PoC | Scanner + Exploit | NTLM Relay → Webshell → SYSTEM
- 2026-11-02
Vendor statements
QuotedCloudflareWAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2026-10-21, 71 days after the CVE was published.
Added: signature 200013238 "Microsoft Exchange MRSProxy Authentication Bypass" (Authentication/Authorization Attacks, risk High), systems: Outlook Web Access. References: CVE-2026-62911.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
Exploit repos · unvetted, don't run
c5z54/cve-2026-62911-poc: CVE-2026-62911 — Exchange MRSProxy Pre-Auth RCE PoC | Scanner + Exploit | NTLM Relay → Webshell → SYSTEM