Patch tracker / KB5120716

KB5120716: Microsoft .NET Framework 4.8 on Window Security Update (August 2026)

KB5120716 is a High security update for Microsoft .NET Framework 4.8 on Window, released 2026-08-11. It closes 3 CVEs with a maximum CVSS of 8.8. The most likely of them to be attacked is CVE-2026-62872, which FIRST.org rates at 6% probability of exploitation in the next 30 days.

Update summary

High

2026-08-11

Released

CVEs fixed

8.8

Max CVSS v3

High

Severity

Deploy this cycle

Fixes 3 CVEs for Microsoft .NET Framework 4.8 on Window. No confirmed in-the-wild exploitation in this set today.

Fixes 3 CVEs. Most severe CVSS 8.8 (High). EPSS exploit probability up to <1%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

Microsoft is not currently aware of any issues in this update.

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5120716 Microsoft support article

Senserva AI Opinion and rich prompt for KB5120716

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

I am an IT admin triaging Microsoft updates. Facts for KB5120716 (source: https://senserva.com/kb/5120716.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed once a day (early morning US Central)):
- Update: KB5120716, Microsoft .NET Framework 4.8 on Window, released 2026-08-11
- Severity: High; fixes 3 CVEs, max CVSS 8.8
- Actively exploited (CISA KEV): no
- CVEs include: CVE-2026-62872, CVE-2026-65810, CVE-2026-70354
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5120716
Using only these facts plus your general knowledge, tell me: 1) How urgent this update is and why, in two sentences. 2) Which systems should get it first. 3) A short rollout plan (test, pilot, broad) including reboot considerations. 4) What to verify after deployment.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for KB5120716

Released: 2026-08-11
Last changed: 2026-08-12
Changes tracked: 2

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 KB5120716 is installed

Elevated PowerShell. No output means it is not installed.

# Is KB5120716 installed? (elevated PowerShell)
Get-HotFix -Id KB5120716 -ErrorAction SilentlyContinue

# Across many machines (replace the names):
Invoke-Command -ComputerName SERVER01,SERVER02 {
  Get-HotFix -Id KB5120716 -ErrorAction SilentlyContinue
} | Select-Object PSComputerName, HotFixID, InstalledOn

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5120716 (checked 2026-08-27). Verify against the article before acting.

Microsoft is not currently aware of any issues in this update.

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-2026-62872	High	8.8	6.2%	No
CVE-2026-65810	High	7.8	6.2%	No
CVE-2026-70354	High	7.8	6.2%	No

Scope and sources

Affected products

Also released in August 2026

Authoritative references

Official KB5120716 page (Microsoft Support)Microsoft Update Catalog Microsoft Security Update Guide

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

KB5120716: Microsoft .NET Framework 4.8 on Window Security Update (August 2026)

Update summary

Full tracking and change history for KB5120716

Check if KB5120716 is installed

Known issues, from Microsoft

CVEs fixed by this update

Scope and sources

KB5002882

KB5002883

KB5002891

KB5120228

KB5120229

KB5120233

KB5120238

KB5120240