Patch tracker / KB5060999
KB5060999: Windows Server 2022 Security Update (June 2025)
KB5060999 is a High security update for Windows Server 2022, released 2025-06-10. It closes 35 CVEs with a maximum CVSS of 8.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. The most likely of them to be attacked is CVE-2025-29828, which FIRST.org rates at 85% probability of exploitation in the next 30 days.
Update summary
Fixes 35 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 85%. Among the top 5% of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows Server 2022 has shipped since this one: KB5073695 (2026-01-13). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 2 known issues with this update.
- Noto fonts issue
- Update delay with deferral policies
KB5060999 is a companion June 2025 package for Windows Server 2022 and Windows 11 version 22H2 ARM64 systems, fixing thirty five of the same CVE-2025-32712 family CVEs as KB5060525 with the identical High severity, CVSS 8.8 top rating, 82 percent EPSS score, and CISA KEV listing. A slightly shorter CVE list than its sibling does not change the fact that the worst bug here is under active attack. Confirm which specific package your update management tooling selected for each device.
Do this: Verify KB5060999 or its sibling update is applied to every Server 2022 and ARM64 Windows 11 22H2 machine.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5060999
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5060999
- Released
- 2025-06-10
- Last changed
- 2026-08-10
- Changes tracked
- 4
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Check if KB5060999 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5060999 (checked 2026-08-10). Verify against the article before acting.
Noto fonts issue
Applies to: All users
Symptoms
There are reports of blurry or unclear CJK (Chinese, Japanese, Korean) text when displayed at 96 DPI (100% scaling) in Chromium-based browsers such as Microsoft Edge and Google Chrome. The March 2025 Preview Update introduced Noto fonts in collaboration with Google, for CJK languages as fallbacks to improve text rendering when websites or apps don’t specify appropriate fonts. The issue is due to limited pixel density at 96 DPI, which can reduce the clarity and alignment of CJK characters. Increasing the display scaling improves clarity by enhancing text rendering.
Workaround
Microsoft has shared its findings on the blurry text issue at 96 DPI, along with potential solutions with Google for further discussion. For additional support, users can report issues related to Noto CJK fonts through the official Google Noto Fonts GitHub repository .
Update delay with deferral policies
Symptoms
Some devices in environments where IT admis use quality update (QU) deferral policies might experience delays in receiving the June 2025 Windows security update. Although the update was released on June 10, 2025, its update metadata timestamp reflects a date of June 20, 2025. This discrepancy might cause devices with configured deferral periods to receive the update later than expected.
Workaround
To accelerate deployment of the June 2025 updates, ...
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2025-33053 | High | 8.8 | 85% | KEV |
| CVE-2025-33073 | High | 8.8 | 85% | KEV |
| CVE-2025-33064 | High | 8.8 | 85% | No |
| CVE-2025-33066 | High | 8.8 | 85% | No |
| CVE-2025-33067 | High | 8.4 | 85% | No |
| CVE-2025-29828 | High | 8.1 | 85% | No |
| CVE-2025-33070 | High | 8.1 | 85% | No |
| CVE-2025-32712 | High | 7.8 | 85% | No |
| CVE-2025-32713 | High | 7.8 | 85% | No |
| CVE-2025-32714 | High | 7.8 | 85% | No |
| CVE-2025-32716 | High | 7.8 | 85% | No |
| CVE-2025-32718 | High | 7.8 | 85% | No |
| CVE-2025-33075 | High | 7.8 | 85% | No |
| CVE-2025-32724 | High | 7.5 | 85% | No |
| CVE-2025-33056 | High | 7.5 | 85% | No |
| CVE-2025-32721 | High | 7.3 | 85% | No |
| CVE-2025-3052 | Medium | 6.7 | 85% | No |
| CVE-2025-32715 | Medium | 6.5 | 85% | No |
| CVE-2025-33057 | Medium | 6.5 | 85% | No |
| CVE-2025-24065 | Medium | 5.5 | 85% | No |
| CVE-2025-24068 | Medium | 5.5 | 85% | No |
| CVE-2025-24069 | Medium | 5.5 | 85% | No |
| CVE-2025-32719 | Medium | 5.5 | 85% | No |
| CVE-2025-32720 | Medium | 5.5 | 85% | No |
| CVE-2025-32722 | Medium | 5.5 | 85% | No |
| CVE-2025-33052 | Medium | 5.5 | 85% | No |
| CVE-2025-33055 | Medium | 5.5 | 85% | No |
| CVE-2025-33058 | Medium | 5.5 | 85% | No |
| CVE-2025-33059 | Medium | 5.5 | 85% | No |
| CVE-2025-33060 | Medium | 5.5 | 85% | No |
| CVE-2025-33061 | Medium | 5.5 | 85% | No |
| CVE-2025-33062 | Medium | 5.5 | 85% | No |
| CVE-2025-33063 | Medium | 5.5 | 85% | No |
| CVE-2025-33065 | Medium | 5.5 | 85% | No |
| CVE-2025-47160 | Medium | 5.4 | 85% | No |
Scope and sources
- Affected products
- Also released in June 2025
KB5058403
34 CVEs · High · exploitedKB5058429
25 CVEs · High · exploitedKB5058430
29 CVEs · High · exploitedKB5058451
34 CVEs · High · exploitedKB5058454
29 CVEs · High · exploitedKB5058497
42 CVEs · High · exploitedKB5060525
39 CVEs · High · exploitedKB5060533
34 CVEs · High · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.