Patch tracker / CVE reference / CVE-2026-25167

CVE-2026-25167

CVE-2026-25167 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 5 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS

4.7%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 4.7%. CVSS 8.8 (High).

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

Senserva AI Opinion for CVE-2026-25167

This Brokering File System elevation-of-privilege flaw is notable for targeting the newest platforms, Windows 11 26H1 and Server 2025 Server Core, at High 8.8 with a low 4 percent EPSS score. An attacker who already has local access could escalate privileges through the brokering component. The modeling rates near-term exploitation as unlikely, but privilege bugs remain useful in a chain. No ransomware use is recorded.

Do this: Include Windows 11 26H1 and Server 2025 Core hosts in the patch cycle and treat this as a defense-in-depth fix against local privilege escalation.

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

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

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-25167 (source: https://senserva.com/cve/CVE-2026-25167.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-25167: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 4.7%
- Actively exploited (CISA KEV): no
- Fixed by: KB5078736, KB5078740, KB5079420, KB5079466, KB5079473
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.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 5%.

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

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-25167

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5078736, KB5078740, KB5079420, KB5079466, KB5079473 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-25167. 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.

KB5078736 KB5078740 KB5079420 KB5079466 KB5079473

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-23667 CVE-2026-23669 CVE-2026-23671 CVE-2026-23672 CVE-2026-23673 CVE-2026-23674 CVE-2026-24282 CVE-2026-24283

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.