Patch tracker / CVE reference / CVE-2025-54105

CVE-2025-54105

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

Risk summary

High

7.0

CVSS

20%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2025-54105

This flaw sits in the Microsoft Brokering File System that mediates file operations on Windows Server 2025 Server Core, Server 2022 23H2 Server Core, and 24H2-based Windows 11 ARM64 builds, and a successful exploit hands a local user full privilege escalation. With a CVSS of 8.8 and roughly a one in five chance of exploitation per EPSS, it is not the most urgent Windows patch this cycle, but skipping it leaves a live local privilege path on the newest server builds.

Do this: Prioritize this patch on Server 2025 and Server 2022 23H2 Server Core hosts, since Server Core boxes often lag standard patch cycles.

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

Senserva AI Opinion and rich prompt for CVE-2025-54105

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-2025-54105 (source: https://senserva.com/cve/CVE-2025-54105.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-54105: High severity Microsoft vulnerability, CVSS 7.0
- EPSS 30-day exploitation probability: 20%
- Actively exploited (CISA KEV): no
- Fixed by: KB5065425, KB5065426, KB5065474
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 KB5065425 and 2 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-2025-54105

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 KB5065425, KB5065426, KB5065474 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-2025-54105. 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.

KB5065425 KB5065426 KB5065474

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-21293 CVE-2025-54106 CVE-2025-54107 CVE-2025-54110 CVE-2025-54113 CVE-2025-54917 CVE-2025-54918 CVE-2025-55234

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.