Patch tracker / CVE reference / CVE-2026-55006

CVE-2026-55006

CVE-2026-55006 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Its EPSS score puts the probability of exploitation in the next 30 days at 20%. Microsoft has shipped the fix: deploy one of the 4 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS

20%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 20%. CVSS 7.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-55006

This is a privilege escalation flaw in on-premises Exchange Server, hitting the 2016 CU23 and 2019 CU14 and CU15 builds that most organizations still run for hybrid or legacy mailbox hosting. Exchange privilege escalation is high value because a foothold here can extend to Active Directory given how Exchange integrates with the directory, and it carries a Severity of High with a CVSS score of 7.8. It is not in the CISA KEV catalog and has no known ransomware use yet, but Exchange bugs are attacked quickly once patches are public.

Do this: Identify all Exchange 2016 CU23 and Exchange 2019 CU14 or CU15 servers and apply the Microsoft security update for CVE-2026-55006 during your next maintenance window.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-55006

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-55006 (source: https://senserva.com/cve/CVE-2026-55006.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-55006: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 20%
- Actively exploited (CISA KEV): no
- Fixed by: KB5103212, KB5103213, KB5103214, KB5103215
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 20%).

Fixed by KB5103212 and 3 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2026-55006

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5103212, KB5103213, KB5103214, KB5103215 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-55006. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5103212 KB5103213 KB5103214 KB5103215

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-55008 CVE-2026-45504 CVE-2026-55005 CVE-2026-45503 CVE-2026-47631 CVE-2026-55009 CVE-2026-45583 CVE-2026-45501

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.