Patch tracker / KB5082123

KB5082123: Windows Server 2019 Security Update (April 2026)

KB5082123 is a Critical security update for Windows Server 2019, released 2026-04-14. It closes 107 CVEs with a maximum CVSS of 9.8. The most likely of them to be attacked is CVE-2026-20930, which FIRST.org rates at 56% probability of exploitation in the next 30 days.

Update summary

Critical
2026-04-14
Released
107
CVEs fixed
9.8
Max CVSS
Critical
Severity
Deploy this cycle
Fixes 107 CVEs for Windows Server 2019. No confirmed in-the-wild exploitation in this set today.

Fixes 107 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 56%. Among the top 25% of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

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, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

  • Domain controllers might restart repeatedly after installing this update

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5082123Microsoft support article
Senserva AI Opinion for KB5082123

KB5082123 is a large April 2026 rollup for Windows 10 1809 and Windows Server 2019 that closes 108 CVEs, topped by a Critical flaw rated CVSS 9.8 with a 64% EPSS score, meaning exploitation is already probable rather than theoretical. At least one of these CVEs is on the CISA KEV list, confirming active exploitation in the wild, though none are currently tied to ransomware campaigns. Anyone still running the 1809 branch or Server 2019 domain infrastructure is directly exposed, and the KEV entry means attackers already know a working path in.

Do this: Deploy KB5082123 to your Server 2019 and Windows 10 1809 hosts now, prioritizing internet-facing and domain-role machines given the KEV-listed CVE.

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

Senserva AI Opinion and rich prompt for KB5082123

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

Full tracking and change history for KB5082123

Released
2026-04-14
Last changed
2026-07-29
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 KB5082123 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5082123 (checked 2026-07-28). Verify against the article before acting.

Domain controllers might restart repeatedly after installing this update

Symptoms

After installing this update, domain controllers in environments with multiple domains in the forest that use Privileged Access Management (PAM), might experience LSASS crashes during startup. As a result, affected domain controllers might restart repeatedly, preventing authentication and directory services from functioning, and potentially rendering the domain unavailable.

Resolution

This issue is addressed in out-of-band update KB5091573 .

Remote Desktop security warnings might not display correctly

Symptoms

After installing this update, the security warning that appears when opening Remote Desktop (RDP) files might not display correctly in some cases.

This issue might occur when you use more than one monitor with different display scaling settings (for example, one display set to 100% and another set to 125%). When this happens, the warning window might show overlapping text or partially hidden buttons, which can make the message difficult to read or interact with.

Resolution

This issue is resolved in Windows updates released on and after May 12, 2026 (such as KB5087538 ). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.

Applies to: Windows 10 Enterprise LTSC 2019

This security update includes ...

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-64720Critical9.856%No
CVE-2025-65018Critical9.856%No
CVE-2026-0390Critical9.856%No
CVE-2026-20806Critical9.856%No
CVE-2026-20928Critical9.856%No
CVE-2026-20930Critical9.856%No
CVE-2026-23670Critical9.856%No
CVE-2026-25250Critical9.856%No
CVE-2026-26151Critical9.856%No
CVE-2026-26152Critical9.856%No
CVE-2026-26153Critical9.856%No
CVE-2026-26154Critical9.856%No
CVE-2026-26155Critical9.856%No
CVE-2026-26156Critical9.856%No
CVE-2026-26159Critical9.856%No
CVE-2026-26160Critical9.856%No
CVE-2026-26161Critical9.856%No
CVE-2026-26162Critical9.856%No
CVE-2026-26163Critical9.856%No
CVE-2026-26167Critical9.856%No
CVE-2026-26168Critical9.856%No
CVE-2026-26169Critical9.856%No
CVE-2026-26170Critical9.856%No
CVE-2026-26173Critical9.856%No
CVE-2026-26174Critical9.856%No
CVE-2026-26175Critical9.856%No
CVE-2026-26176Critical9.856%No
CVE-2026-26177Critical9.856%No
CVE-2026-26178Critical9.856%No
CVE-2026-26180Critical9.856%No
CVE-2026-26182Critical9.856%No
CVE-2026-26183Critical9.856%No
CVE-2026-26184Critical9.856%No
CVE-2026-27908Critical9.856%No
CVE-2026-27909Critical9.856%No
CVE-2026-27910Critical9.856%No
CVE-2026-27911Critical9.856%No
CVE-2026-27912Critical9.856%No
CVE-2026-27913Critical9.856%No
CVE-2026-27914Critical9.856%No
CVE-2026-27915Critical9.856%No
CVE-2026-27916Critical9.856%No
CVE-2026-27917Critical9.856%No
CVE-2026-27918Critical9.856%No
CVE-2026-27919Critical9.856%No
CVE-2026-27920Critical9.856%No
CVE-2026-27921Critical9.856%No
CVE-2026-27922Critical9.856%No
CVE-2026-27923Critical9.856%No
CVE-2026-27925Critical9.856%No
CVE-2026-27926Critical9.856%No
CVE-2026-27927Critical9.856%No
CVE-2026-27928Critical9.856%No
CVE-2026-27929Critical9.856%No
CVE-2026-27930Critical9.856%No
CVE-2026-32068Critical9.856%No
CVE-2026-32069Critical9.856%No
CVE-2026-32070Critical9.856%No
CVE-2026-32071Critical9.856%No
CVE-2026-32072Critical9.856%No
CVE-2026-32073Critical9.856%No
CVE-2026-32074Critical9.856%No
CVE-2026-32075Critical9.856%No
CVE-2026-32077Critical9.856%No
CVE-2026-32078Critical9.856%No
CVE-2026-32079Critical9.856%No
CVE-2026-32080Critical9.856%No
CVE-2026-32081Critical9.856%No
CVE-2026-32082Critical9.856%No
CVE-2026-32083Critical9.856%No
CVE-2026-32084Critical9.856%No
CVE-2026-32085Critical9.856%No
CVE-2026-32086Critical9.856%No
CVE-2026-32087Critical9.856%No
CVE-2026-32088Critical9.856%No
CVE-2026-32089Critical9.856%No
CVE-2026-32090Critical9.856%No
CVE-2026-32091Critical9.856%No
CVE-2026-32093Critical9.856%No
CVE-2026-32149Critical9.856%No
CVE-2026-32150Critical9.856%No
CVE-2026-32151Critical9.856%No
CVE-2026-32153Critical9.856%No
CVE-2026-32154Critical9.856%No
CVE-2026-32156Critical9.856%No
CVE-2026-32157Critical9.856%No
CVE-2026-32158Critical9.856%No
CVE-2026-32159Critical9.856%No
CVE-2026-32160Critical9.856%No
CVE-2026-32162Critical9.856%No
CVE-2026-32163Critical9.856%No
CVE-2026-32164Critical9.856%No
CVE-2026-32165Critical9.856%No
CVE-2026-32183Critical9.856%No
CVE-2026-32212Critical9.856%No
CVE-2026-32214Critical9.856%No
CVE-2026-32215Critical9.856%No
CVE-2026-32217Critical9.856%No
CVE-2026-32225Critical9.856%No
CVE-2026-33098Critical9.856%No
CVE-2026-33099Critical9.856%No
CVE-2026-33100Critical9.856%No
CVE-2026-33104Critical9.856%No
CVE-2026-33824Critical9.856%No
CVE-2026-33826Critical9.856%No
CVE-2026-33827Critical9.856%No
CVE-2026-33829Critical9.856%No

Scope and sources

Affected products
Also released in April 2026

KB5002853

2 CVEs · Medium · exploited

KB5002854

2 CVEs · Medium · exploited

KB5002861

2 CVEs · Medium · exploited

KB5082052

115 CVEs · Critical

KB5082060

121 CVEs · Critical

KB5082063

124 CVEs · Critical

KB5082142

116 CVEs · Critical

KB5082198

87 CVEs · Critical

The full month, summarized: Microsoft Patch Tuesday.

Authoritative references
Official KB5082123 page (Microsoft Support)Microsoft Update CatalogMicrosoft Security Update Guide

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

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.