CVE-2022-41082: Microsoft Exchange Server Remote PowerShell RCE (ProxyNotShell component)
- Vendor
- Microsoft Corporation
CVE-2022-41082 is an insecure deserialization vulnerability affecting on-premises Microsoft Exchange Server 2013, 2016, and 2019. An authenticated attacker who can access Exchange Remote PowerShell can trigger arbitrary code execution on the server. It is the code-execution component of ProxyNotShell, which chains it with CVE-2022-41040 to reach PowerShell through server-side request forgery, and OWASSRF, which chains it with CVE-2022-41080 through Outlook Web Access. Both chains have been exploited in the wild. Exchange Online is unaffected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code and PowerShell command execution on a vulnerable Exchange server, potentially compromising the Exchange environment and the confidentiality, integrity, and availability of hosted email. Attackers can use the resulting access to install backdoors, steal credentials and data, and move laterally into connected infrastructure. Observed exploitation chains have supported persistent access and ransomware operations.
Mitigation
If you can’t patch tonight, do this now.
Until patching is possible, restrict Exchange and Remote PowerShell access through firewall or VPN controls, disable Remote PowerShell for non-administrative users where feasible, and disable Outlook Web Access if necessary to prevent OWASSRF exposure. Historical ProxyNotShell IIS URL Rewrite or WAF filters are not sufficient protection because OWASSRF bypasses those mitigations. Restrict outbound connections from Exchange servers using allow lists, and monitor for suspicious Exchange requests, unexpected PowerShell activity, and webshell behavior. Network restrictions do not protect against attackers who already have internal access.
Remediation
Patch, then assume compromise.
Apply the applicable Microsoft Exchange security updates released on November 8, 2022, covered by KB5019758, or a later applicable update incorporating those fixes. These updates address CVE-2022-41082 and its associated chaining vulnerabilities, CVE-2022-41040 and CVE-2022-41080. Verify installation and investigate potentially exposed servers for prior exploitation; patching does not remove existing backdoors.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-41082 exploited in the wild?
- Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 30, 2022.
- Is there a public exploit for CVE-2022-41082?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2022-41082, the earliest disclosed Sep 28, 2022.
- Is there a patch for CVE-2022-41082?
- Apply the applicable Microsoft Exchange security updates released on November 8, 2022, covered by KB5019758, or a later applicable update incorporating those fixes. These updates address CVE-2022-41082 and its associated chaining vulnerabilities, CVE-2022-41040 and CVE-2022-41080.
- What products are affected by CVE-2022-41082?
- Microsoft Corporation Exchange Server.
- How severe is CVE-2022-41082?
- CVE-2022-41082 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
Recent activity
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.