Patch tracker / KB5049984

KB5049984: Windows Server 2019 Security Update (January 2025)

KB5049984 is a Critical security update for Windows Server 2019, released 2025-01-14. It closes 128 CVEs with a maximum CVSS of 9.8. At least one of them is actively exploited (CISA KEV), so this is a deploy-first update. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.

CriticalCISA KEV
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-01-14. Fixes 128 CVEs.

Download KB5049984Senserva AI read on KB5049984Install guidanceKnown issuesIs it installed?CVEs it fixesChange history#34 hottest Microsoft patch right now

Exploitation is not theoretical here: at least one CVE this update fixes is on the CISA Known Exploited Vulnerabilities catalog, which means attackers are already using it against unpatched systems. For an update like this, the risk window is the gap between today and the day your last device installs it, so shortening that gap matters more than perfect scheduling.

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, including how to expedite it for the exploited CVE. 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 now
This update fixes vulnerabilities confirmed exploited in the wild.
Download KB5049984 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 KB5049984

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

Update summary

Released
2025-01-14
CVEs fixed
128
Max CVSS
9.8
Severity
Critical

Senserva AI Opinion for KB5049984

KB5049984 matches KB5050009's one hundred twenty eight CVE count for January 2025 on Windows 10 version 1809 and Windows Server 2019, with the same Critical severity, CVSS 9.8 top flaw, 81 percent EPSS score, and CISA KEV listing. Multiple nearly identical packages this month reflect Microsoft's split by servicing branch, but the risk profile is the same wherever it lands. Confirm your update ring is not silently skipping this in favor of an older baseline.

Do this: Verify KB5049984 installs successfully on all applicable Windows 10 1809 and Windows Server 2019 machines.

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

Senserva AI Opinion and rich prompt for KB5049984

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

Full tracking and change history for KB5049984

Released
2025-01-14
Last changed
2025-01-14
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 128 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 81%.

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

What to do

Treat as urgent: it is being exploited in the wild (CISA KEV), so patch ahead of items that are not. Senserva flags whether KB5049984 is missing on your devices.

Check if KB5049984 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.

Known issues, from Microsoft

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

|

| Symptom

| Workaround

| Following the installation of the October 2024 security update, some customers report that the OpenSSH (Open Secure Shell) service fails to start, preventing SSH connections. The service fails with no detailed logging, and manual intervention is required to run the sshd.exe process.This issue is affecting both enterprise, IOT, and education customers, with a limited number of devices impacted. Microsoft is investigating whether consumer customers using Home or Pro editions of Windows are affected.

| This issue is addressed in KB5053599 .

Writing about KB5049984? 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-21333Critical9.881%KEV
CVE-2025-21334Critical9.881%KEV
CVE-2025-21335Critical9.881%KEV
CVE-2024-49120Critical9.883%No
CVE-2024-7344Critical9.881%No
CVE-2025-21189Critical9.881%No
CVE-2025-21193Critical9.881%No
CVE-2025-21202Critical9.881%No
CVE-2025-21207Critical9.881%No
CVE-2025-21210Critical9.881%No
CVE-2025-21211Critical9.881%No
CVE-2025-21213Critical9.881%No
CVE-2025-21214Critical9.881%No
CVE-2025-21215Critical9.881%No
CVE-2025-21217Critical9.881%No
CVE-2025-21218Critical9.881%No
CVE-2025-21219Critical9.881%No
CVE-2025-21220Critical9.881%No
CVE-2025-21223Critical9.881%No
CVE-2025-21224Critical9.881%No
CVE-2025-21225Critical9.881%No
CVE-2025-21226Critical9.881%No
CVE-2025-21227Critical9.881%No
CVE-2025-21228Critical9.881%No
CVE-2025-21229Critical9.881%No
CVE-2025-21230Critical9.881%No
CVE-2025-21231Critical9.881%No
CVE-2025-21232Critical9.881%No
CVE-2025-21233Critical9.881%No
CVE-2025-21234Critical9.881%No
CVE-2025-21235Critical9.881%No
CVE-2025-21236Critical9.881%No
CVE-2025-21237Critical9.881%No
CVE-2025-21238Critical9.881%No
CVE-2025-21239Critical9.881%No
CVE-2025-21240Critical9.881%No
CVE-2025-21241Critical9.881%No
CVE-2025-21242Critical9.881%No
CVE-2025-21243Critical9.881%No
CVE-2025-21244Critical9.881%No
CVE-2025-21245Critical9.881%No
CVE-2025-21246Critical9.881%No
CVE-2025-21248Critical9.881%No
CVE-2025-21249Critical9.881%No
CVE-2025-21250Critical9.881%No
CVE-2025-21251Critical9.881%No
CVE-2025-21252Critical9.881%No
CVE-2025-21255Critical9.881%No
CVE-2025-21256Critical9.881%No
CVE-2025-21257Critical9.881%No
CVE-2025-21258Critical9.881%No
CVE-2025-21260Critical9.881%No
CVE-2025-21261Critical9.881%No
CVE-2025-21263Critical9.881%No
CVE-2025-21265Critical9.881%No
CVE-2025-21266Critical9.881%No
CVE-2025-21268Critical9.881%No
CVE-2025-21269Critical9.881%No
CVE-2025-21270Critical9.881%No
CVE-2025-21272Critical9.881%No
CVE-2025-21273Critical9.881%No
CVE-2025-21274Critical9.881%No
CVE-2025-21275Critical9.881%No
CVE-2025-21276Critical9.881%No
CVE-2025-21277Critical9.881%No
CVE-2025-21278Critical9.881%No
CVE-2025-21280Critical9.881%No
CVE-2025-21281Critical9.881%No
CVE-2025-21282Critical9.881%No
CVE-2025-21284Critical9.881%No
CVE-2025-21285Critical9.881%No
CVE-2025-21286Critical9.881%No
CVE-2025-21287Critical9.881%No
CVE-2025-21288Critical9.881%No
CVE-2025-21289Critical9.881%No
CVE-2025-21290Critical9.881%No
CVE-2025-21291Critical9.881%No
CVE-2025-21292Critical9.881%No
CVE-2025-21293Critical9.881%No
CVE-2025-21294Critical9.881%No
CVE-2025-21295Critical9.881%No
CVE-2025-21296Critical9.881%No
CVE-2025-21297Critical9.881%No
CVE-2025-21298Critical9.881%No
CVE-2025-21299Critical9.881%No
CVE-2025-21300Critical9.881%No
CVE-2025-21301Critical9.881%No
CVE-2025-21302Critical9.881%No
CVE-2025-21303Critical9.881%No
CVE-2025-21305Critical9.881%No
CVE-2025-21306Critical9.881%No
CVE-2025-21307Critical9.881%No
CVE-2025-21309Critical9.881%No
CVE-2025-21310Critical9.881%No
CVE-2025-21311Critical9.881%No
CVE-2025-21312Critical9.881%No
CVE-2025-21313Critical9.881%No
CVE-2025-21314Critical9.881%No
CVE-2025-21315Critical9.881%No
CVE-2025-21316Critical9.881%No
CVE-2025-21317Critical9.881%No
CVE-2025-21318Critical9.881%No
CVE-2025-21319Critical9.881%No
CVE-2025-21320Critical9.881%No
CVE-2025-21321Critical9.881%No
CVE-2025-21323Critical9.881%No
CVE-2025-21324Critical9.881%No
CVE-2025-21326Critical9.881%No
CVE-2025-21327Critical9.881%No
CVE-2025-21328Critical9.881%No
CVE-2025-21329Critical9.881%No
CVE-2025-21330Critical9.881%No
CVE-2025-21331Critical9.881%No
CVE-2025-21332Critical9.881%No
CVE-2025-21336Critical9.881%No
CVE-2025-21338Critical9.881%No
CVE-2025-21339Critical9.881%No
CVE-2025-21340Critical9.881%No
CVE-2025-21341Critical9.881%No
CVE-2025-21372Critical9.881%No
CVE-2025-21374Critical9.881%No
CVE-2025-21378Critical9.881%No
CVE-2025-21382Critical9.881%No
CVE-2025-21389Critical9.881%No
CVE-2025-21409Critical9.881%No
CVE-2025-21411Critical9.881%No
CVE-2025-21413Critical9.881%No
CVE-2025-21417Critical9.881%No

Also released in January 2025

The highest-risk updates from the same release:

The full month, summarized: Microsoft Patch Tuesday.

How to install KB5049984

Any of these paths delivers KB5049984; 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. For this update, consider an expedite policy: it bypasses deferrals for exactly this fix-now case.
  • Windows Autopatch: rings, rollout, and pause or rollback are managed for you; exploited updates can be expedited.
  • WSUS / Configuration Manager: approve KB5049984 for your device groups and set a deadline (deadline, not just approval, for an exploited fix).
  • 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 KB5049984, ranked by exploitation.

Common questions about KB5049984

Does KB5049984 have known issues?

Yes. Microsoft's support article documents known issues for KB5049984 (checked 2026-07-22). The Known issues section on this page quotes it; verify against the article before acting.

Is KB5049984 urgent?

Yes. KB5049984 fixes at least one vulnerability in the CISA Known Exploited Vulnerabilities catalog, meaning attackers are using it in the wild. Deploy it first.

How do I download KB5049984?

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 KB5049984 with Intune?

Assign a Windows Update ring (quality update policy) to the device groups and the update flows on the ring's deferral schedule. Because KB5049984 fixes an actively exploited CVE, an Intune expedite policy is the right tool: it bypasses configured deferrals and pushes the update as soon as devices check in. Verify the rollout with update compliance reporting rather than assuming delivery.

Can I ask my own AI about KB5049984?

Yes. This page includes a free, ready-to-paste AI prompt containing KB5049984'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.