Patch tracker / KB5062618

KB5062618: Windows Server 2019 Security Update (August 2025)

KB5062618 is a High security update for Windows Server 2019, released 2025-08-12. It closes 51 CVEs with a maximum CVSS of 8.8. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.

High
A newer security update for Windows 10 Version 1809 for 32-bit Systems has shipped since this one: KB5089548 (2026-07-14). For cumulative update families the newer package includes these fixes.

Microsoft security update released 2025-08-12. Fixes 51 CVEs.

Download KB5062618Senserva AI read on KB5062618Install guidanceIs it installed?CVEs it fixesChange history

No exploitation is confirmed yet, but the EPSS model puts the 30-day exploitation probability for the worst CVE here at 14%, which is high enough to treat this as more urgent than its High label alone suggests. Attackers reverse-engineer Patch Tuesday updates within days, so the safe assumption is that exploit code follows the patch.

Most organizations deliver an update like this automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; the install section below covers each path. For the bigger picture: how the Microsoft patching tools fit together, this month's Patch Tuesday summary, and every update ranked by real-world risk.

Deploy this cycle
Fixes 51 CVEs for Windows Server 2019. No confirmed in-the-wild exploitation in this set today.
Download KB5062618 from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS. The full CVE list is below.

Updated July 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Download KB5062618

Get the official update for KB5062618. The download and file size for each supported product are on the Microsoft Update Catalog page.

Update summary

Released
2025-08-12
CVEs fixed
51
Max CVSS
8.8
Severity
High

Senserva AI Opinion for KB5062618

KB5062618 is the August 12, 2025 rollup for Windows 10 Version 1809 and Windows Server 2019, closing 51 vulnerabilities including CVE-2025-55230 and CVE-2025-48824. The top issue rates High at CVSS 8.8, but none of these CVEs are in the CISA KEV catalog or tied to known ransomware, and the highest EPSS exploitation probability sits at 14 percent. This matters most for the aging 1809 and Server 2019 fleet that many organizations still run for legacy application compatibility.

Do this: Deploy KB5062618 to your remaining Windows 10 1809 and Server 2019 hosts this cycle, prioritizing internet-facing Server 2019 systems.

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

Senserva AI Opinion and rich prompt for KB5062618

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

Full tracking and change history for KB5062618

Released
2025-08-12
Last changed
2025-08-12
Changes tracked
1

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.

Exploitation and severity

Fixes 51 CVEs. Most severe CVSS 8.8 (High). EPSS exploit probability up to 14%.

Among the top half of tracked Microsoft updates by EPSS exploit probability.

What to do

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. Senserva flags whether KB5062618 is missing on your devices.

Check if KB5062618 is installed

Copy-paste PowerShell: one machine, or your whole fleet in one pass. No output means the update is not installed.

Get-HotFix covers Windows updates. Office, SharePoint, and Exchange server updates show under installed updates in Programs and Features, or check the Update Catalog history.

Writing about KB5062618? Cite this page

Copy-paste for a blog post, forum answer, or internal doc. The link always carries the current risk data.

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.

CVESeverityCVSSEPSSExploited
CVE-2025-47971Critical9.822%No
CVE-2025-47973Critical9.822%No
CVE-2025-47975Critical9.822%No
CVE-2025-47976Critical9.822%No
CVE-2025-47980Critical9.822%No
CVE-2025-47984Critical9.822%No
CVE-2025-47985Critical9.822%No
CVE-2025-47986Critical9.822%No
CVE-2025-47987Critical9.822%No
CVE-2025-47996Critical9.822%No
CVE-2025-47998Critical9.822%No
CVE-2025-48805Critical9.822%No
CVE-2025-48806Critical9.822%No
CVE-2025-48808Critical9.822%No
CVE-2025-48815Critical9.822%No
CVE-2025-48816Critical9.822%No
CVE-2025-48817Critical9.822%No
CVE-2025-48819Critical9.822%No
CVE-2025-48821Critical9.822%No
CVE-2025-48824Critical9.822%No
CVE-2025-49657Critical9.822%No
CVE-2025-49658Critical9.822%No
CVE-2025-49659Critical9.822%No
CVE-2025-49661Critical9.822%No
CVE-2025-49663Critical9.822%No
CVE-2025-49668Critical9.822%No
CVE-2025-49669Critical9.822%No
CVE-2025-49670Critical9.822%No
CVE-2025-49671Critical9.822%No
CVE-2025-49672Critical9.822%No
CVE-2025-49673Critical9.822%No
CVE-2025-49674Critical9.822%No
CVE-2025-49675Critical9.822%No
CVE-2025-49676Critical9.822%No
CVE-2025-49678Critical9.822%No
CVE-2025-49679Critical9.822%No
CVE-2025-49681Critical9.822%No
CVE-2025-49683Critical9.822%No
CVE-2025-49686Critical9.822%No
CVE-2025-49689Critical9.822%No
CVE-2025-49716Critical9.822%No
CVE-2025-49721Critical9.822%No
CVE-2025-49722Critical9.822%No
CVE-2025-49727Critical9.822%No
CVE-2025-49729Critical9.822%No
CVE-2025-49730Critical9.822%No
CVE-2025-49732Critical9.822%No
CVE-2025-49742Critical9.822%No
CVE-2025-49753Critical9.822%No
CVE-2025-49757Critical9.822%No
CVE-2025-55230Critical9.822%No

Also released in August 2025

The highest-risk updates from the same release:

The full month, summarized: Microsoft Patch Tuesday.

How to install KB5062618

Any of these paths delivers KB5062618; most organizations already have one of the first three running:

  • Intune update rings (Windows Update for Business): the update flows on each ring's deferral schedule.
  • Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
  • WSUS / Configuration Manager: approve KB5062618 for your device groups and set a deadline.
  • Manual: download from the Update Catalog above and install; fine for a handful of machines, unmanageable at any real scale.

After the rollout, verify rather than assume: update compliance reporting in Intune or Autopatch shows which devices actually installed it, and Siemserva reads Intune, Defender, Autopatch, and Azure Update Manager together to show the devices still missing KB5062618, ranked by exploitation.

Common questions about KB5062618

Is KB5062618 urgent?

KB5062618 is rated High. Include it in your normal patch cycle unless your environment raises its priority.

How do I download KB5062618?

From the Microsoft Update Catalog (linked on this page), or let Intune, Windows Update for Business, Windows Autopatch, or WSUS deliver it. The catalog page lists the download for each supported product.

How do I deploy KB5062618 with Intune?

Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. For urgent updates, Intune expedite policies can bypass the ring deferrals. Verify the rollout with update compliance reporting rather than assuming delivery.

Can I ask my own AI about KB5062618?

Yes. This page includes a free, ready-to-paste AI prompt containing KB5062618's key facts: severity, CVE count, exploitation status, and the download link. Copy it into Claude, ChatGPT, or Copilot for a rollout plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).

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

Three Free Unlimited Audits: all users, all settings, all patches, all tenants. All you do is register.

Three free audits, across every tenant you manage: 1 scan to find, 2 to review your fixes. It finds:

Includes our advanced Claude MCP: everything you need to run full audits.

Lexicon: the terms on this page
CVE
Common Vulnerabilities and Exposures. A unique ID for one publicly known vulnerability, such as CVE-2025-1234.
KB
Microsoft Knowledge Base article. The identifier for a specific Microsoft update.
KEV
CISA Known Exploited Vulnerabilities. CVEs confirmed exploited in the wild. Fix these first.
CVSS
Common Vulnerability Scoring System. A standardized Severity score from 0 to 10.
EPSS
Exploit Prediction Scoring System. The probability a CVE will be exploited in the next 30 days.
MSRC
Microsoft Security Response Center. Microsoft's Patch Tuesday advisories and KB-to-CVE mapping.
NVD
National Vulnerability Database (NIST). Authoritative CVE metadata and CVSS scores.
Ransomware
The vulnerability is linked to known ransomware activity.
Reference: Microsoft CVE and vulnerability management, the full CVE-to-patch lookup ranked by real-world risk, and the Microsoft patching guide, how Intune, Windows Autopatch, Defender, and Azure Update Manager fit together.
Data notice: this page, the feeds, and the API are provided as is, for informational purposes only, without warranty of any kind. Senserva, LLC does not guarantee the accuracy, completeness, or timeliness of third-party data (MSRC, NVD, CISA KEV, EPSS) and accepts no liability for actions taken based on it; verify against the authoritative vendor advisory before acting. Built daily with Senserva Trustworthy AI. All use of this data is subject to the Senserva EULA.