CVE-2022-41040
CVE-2022-41040 is a security flaw in Microsoft Exchange Server, Microsoft’s email server, which companies run for their staff’s mail. Attackers can run their own code on Microsoft Exchange Server. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 30 Sep 2022, and says ransomware gangs have used it.[1]
Microsoft Exchange Server is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version 15.00.1497.044, 15.01.2375.037, 15.02.0986.036 and 15.02.1118.020 and others.
Description
CISA calls it a server-side request forgery in Microsoft Exchange Server. In its words: “Microsoft Exchange Server allows for server-side request forgery. Dubbed "ProxyNotShell," this vulnerability is chainable with CVE-2022-41082 which allows for remote code execution.”[1]
The underlying weakness is server-side request forgery (CWE-918), in MITRE’s list of common software weaknesses.[2]
It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]
| Product | Fixed in |
|---|---|
| Microsoft Exchange Server 2013 Cumulative Update 23 | 15.00.1497.044 |
| Microsoft Exchange Server 2016 Cumulative Update 22 | 15.01.2375.037 |
| Microsoft Exchange Server 2019 Cumulative Update 11 | 15.02.0986.036 |
| Microsoft Exchange Server 2019 Cumulative Update 12 | 15.02.1118.020 |
| Microsoft Exchange Server 2016 Cumulative Update 23 | 15.01.2507.016 |
Most families won’t have Microsoft Exchange Server; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 30 Sep 2022. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 21 Oct 2022 to fix it.[1] CISA says ransomware gangs have used it.
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Microsoft has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]
- Check whether you use it.Microsoft Exchange Server is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version 15.00.1497.044, 15.01.2375.037, 15.02.0986.036 and 15.02.1118.020 and others), or not in use. CISA gave US government agencies until 21 Oct 2022 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| CISA adds it to its catalog of flaws known to be used in attacks, noting that ransomware gangs have used it.[1] | |
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4] |
See also
Other Microsoft Exchange Server flaws
- CVE-2023-21529: deserialization of untrusted data ·
- CVE-2021-31196: information disclosure ·
- CVE-2024-21410: privilege escalation ·
- CVE-2022-41080: privilege escalation ·
- CVE-2022-41082: remote code execution ·
- CVE-2018-8581: privilege escalation ·
Other Microsoft flaws
- CVE-2026-96951, Microsoft Windows: command injection ·
- CVE-2026-65660, Microsoft SharePoint: code injection ·
- CVE-2026-85880, Microsoft Windows: heap-based buffer overflow ·
- CVE-2026-81963, Microsoft Windows: link following ·
- CVE-2019-1068, Microsoft SQL Server: remote code execution ·
Other server-side request forgery flaws
- CVE-2026-96655, Plex Media Server: server-side request forgery (SSRF) ·
- CVE-2026-96652, Plex Media Server: server-side request forgery (SSRF) ·
- CVE-2026-83548, SonicWall SMA1000 Appliances: server-side request forgery ·
- CVE-2026-64849, MLflow: server-side request forgery ·
- CVE-2026-15409, SonicWall SMA1000 Appliances: server-side request forgery ·
Added the same day
- CVE-2022-41082, Microsoft Exchange Server: remote code execution ·
- CVE-2022-36804, Atlassian Bitbucket Server and Data Center: command injection ·
Every Microsoft flaw on CISA’s list · Everything added in September 2022
References
- ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Exchange Server Server-Side Request Forgery Vulnerability”. Known Exploited Vulnerabilities Catalog, added 30 Sep 2022.
- ^ National Institute of Standards and Technology. “CVE-2022-41040 Detail”. National Vulnerability Database, published 3 Oct 2022.
- ^ Microsoft. Advisories and fixes: msrc-blog.microsoft.com, msrc.microsoft.com, portal.msrc.microsoft.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 1.000, percentile 100.0, 31 Oct 2026.
- CVE Program. “CVE-2022-41040”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.