Microsoft Exchange Server Tampering Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Microsoft Exchange Server 2016 Cumulative Update 23 15.01.2507.073; Microsoft Exchange Server 2019 Cumulative Update 14 15.02.1544.046; Microsoft Exchange Server 2019 Cumulative Update 15 15.02.1748.051.
Low priority for now. Upgrade to Microsoft Exchange Server 2016 Cumulative Update 23 15.01.2507.073; Microsoft Exchange Server 2019 Cumulative Update 14 15.02.1544.046; Microsoft Exchange Server 2019 Cumulative Update 15 15.02.1748.051 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Authorization bypass through user-controlled key in Microsoft Exchange Server allows an authorized attacker to perform tampering over a network.
- Published
- Sep 8, 2026
- Updated
- Oct 8, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-639
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | exchange server | cpe:2.3:a:microsoft:exchange_server |
| microsoft | exchange server subscription edition | cpe:2.3:a:microsoft:exchange_server_subscription_edition |
Using exchange server? Add it to your stack and be the first to know about CVEs like this one. (Email server)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft exchange server2016
- microsoft exchange server2019
- microsoft exchange server subscription editionbefore 15.02.2562.049
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft Exchange Server 2016 Cumulative Update 23
- 15.01.0.0 and later · before 15.01.2507.073affected
Microsoft Microsoft Exchange Server 2019 Cumulative Update 14
- 15.02.0.0 and later · before 15.02.1544.046affected
Microsoft Microsoft Exchange Server 2019 Cumulative Update 15
- 15.02.0.0 and later · before 15.02.1748.051affected
Microsoft Microsoft Exchange Server Subscription Edition RTM
- 15.02.0.0 and later · before 15.02.2562.049affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34523Microsoft Exchange Server Elevation of Privilege VulnerabilityKEV96Now
- CVE-2021-34473Microsoft Exchange Server Remote Code Execution VulnerabilityKEV96Now
- CVE-2021-26855Microsoft Exchange Server Remote Code Execution VulnerabilityKEV96Now
- CVE-2022-41040Microsoft Exchange Server Elevation of Privilege VulnerabilityKEV95Now
- CVE-2020-0688A remote code execution vulnerability exists in Microsoft Exchange software when the software fails to properly handle objects in memory, akKEV95Now
- CVE-2021-42321Microsoft Exchange Server Remote Code Execution VulnerabilityKEV93Now
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Microsoft Exchange Server 2016 Cumulative Update 23 | 15.01.2507.073 · KB5121611 | Microsoft (MSRC) |
| Microsoft Exchange Server 2019 Cumulative Update 14 | 15.02.1544.046 · KB5121610 | Microsoft (MSRC) |
| Microsoft Exchange Server 2019 Cumulative Update 15 | 15.02.1748.051 · KB5121609 | Microsoft (MSRC) |
| Microsoft Exchange Server Subscription Edition RTM | 15.02.2562.049 · KB5121608 | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);res.json(invoice);Fixed
const invoice = await Invoice.findOne({ id: req.params.id, ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.