Patch tracker / CVE reference / CVE-2025-53798
CVE-2025-53798
CVE-2025-53798 is a medium severity Microsoft vulnerability with a CVSS score of 6.5. Its EPSS score puts the probability of exploitation in the next 30 days at 20%. Microsoft has shipped the fix: deploy one of the 13 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 20%. CVSS 6.5 (Medium).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
A second RRAS information disclosure CVE from the same release as the one above, identical severity, EPSS, and affected servers. This pattern of paired or grouped RRAS CVEs each cycle is now a fixture of Patch Tuesday and worth budgeting recurring attention for.
Do this: Cover this with the same RRAS focused patch and role audit as its sibling CVE from this cycle.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-53798
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2025-53798
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 KB5065306, KB5065425, KB5065426, KB5065427, KB5065428, KB5065432, KB5065468, KB5065474, KB5065507, KB5065508, KB5065509, KB5065510, KB5065511 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-53798. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.