Loading story…
A critical Microsoft Exchange Server flaw, CVE-2021-34473, enabled unauthenticated attackers to reach privileged backend services through improper URI validation and URL normalization in the Client Access Service and autodiscover functionality. The bug is the first stage of the ProxyShell attack chain and has been widely tied to in-the-wild exploitation, with affected builds including Exchange Server 2013 CU23, Exchange Server 2016 CU19 and CU20, and Exchange Server 2019 CU8 and CU9.
Attackers have used the issue to bypass authentication, access Exchange PowerShell, read mailboxes, deploy webshells, exfiltrate email, and move laterally, especially when chaining it with CVE-2021-34523 and CVE-2021-31207 for full compromise. Public exploitation resources, including GitHub tooling and scanning templates, lowered the barrier to abuse, while defenders were urged to apply Microsoft's security updates, hunt for webshell indicators and suspicious autodiscover requests, monitor for PowerShell launched by w3wp.exe, and reduce external exposure of Exchange services.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
The SentinelOne reference says CVE-2021-34473 is included in CISA's Known Exploited Vulnerabilities Catalog, reflecting official recognition of exploitation risk.
Source content states that CVE-2021-34473, part of the ProxyShell attack chain, has been actively exploited in real-world attacks against Microsoft Exchange Server.
The source content recommends applying Microsoft's security updates for CVE-2021-34473 to mitigate the Exchange Server vulnerability that underpins the ProxyShell chain.
The GitHub reference describes publicly available exploitation resources for ProxyShell, including Python scripts and a Nuclei scanning template, indicating technical details and tooling were released publicly.
The ProxyShell set of Microsoft Exchange vulnerabilities, centered on CVE-2021-34473 and chainable with CVE-2021-34523 and CVE-2021-31207, is attributed in the source content to Orange Tsai at Pwn2Own.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers detailed **ProxyShell**, a chain of Microsoft Exchange vulnerabilities that can be combined to bypass authentication, escalate privileges, and achieve remote code execution on exposed Exchange servers. Orange Tsai described the attack surface and showed how flaws including `CVE-2021-34473`, `CVE-2021-34523`, and `CVE-2021-31207` could be chained to reach backend Exchange services and execute attacker-controlled code without valid credentials. Mandiant later reported real-world exploitation of ProxyShell against internet-facing Exchange environments, showing that attackers used the chain to gain shells on compromised servers and establish persistent access. The reporting underscores that unpatched on-premises Exchange systems remained a high-value target because successful exploitation could hand attackers direct control of email infrastructure, enable follow-on intrusion activity, and expose sensitive enterprise communications.
Jul 12, 2026
Attackers exploited the **ProxyNotShell** chain on on-premises Microsoft Exchange Server by combining `CVE-2022-41040`, an authenticated SSRF flaw, with `CVE-2022-41082`, a remote code execution bug reachable through Exchange PowerShell remoting. Microsoft confirmed that Exchange Server **2013, 2016, and 2019** were affected, and the flaws were reported as being used against critical infrastructure before patches were released. The intrusion path exposed the Exchange PowerShell endpoint through crafted requests and then abused `WSMAN` and XML SOAP traffic to establish remote shell access. Observed post-exploitation activity included reconnaissance, DLL hijacking attempts, remote process injection, persistence, and reverse shell deployment. Investigators also documented deserialization-based execution triggered through a crafted address book request, along with malicious DLLs and binaries, a reverse proxy executable, and command-and-control infrastructure including `193.149.185.52:443` and `sync.service.auzreservices.com`, indicating that successful exploitation quickly progressed from initial access to hands-on-keyboard control.
Jun 29, 2026
Microsoft disclosed multiple vulnerabilities in on-premises **Exchange Server**, including **CVE-2021-31207** (security feature bypass), **CVE-2021-31209** (spoofing), and **CVE-2022-41040** (elevation of privilege). The issues affected Exchange deployments rather than **Exchange Online**, extending a pattern of high-impact weaknesses in the mail platform that could undermine trust boundaries, enable impersonation, and weaken built-in protections. Among them, **CVE-2022-41040** was rated **Critical** with a **CVSS 3.1 score of 8.8**, and Microsoft said exploitation had been detected in the wild before public disclosure. The flaw required an authenticated attacker with low privileges and no user interaction, and successful exploitation could allow the attacker to run **PowerShell** as **`SYSTEM`**. Microsoft later released security updates and directed Exchange Server customers to apply mitigations and patches for the reported zero-day issues.
Jun 29, 2026