Patch tracker / KB5099539
KB5099539: Windows Server 2019 Security Update (July 2026)
KB5099539 is a Critical security update for Windows Server 2019, released 2026-07-14. It closes 313 CVEs with a maximum CVSS of 9.9. Get it from the Microsoft Update Catalog below, and see where it sits against the rest of the month on the patch tracker.
Microsoft security update released 2026-07-14. Fixes 313 CVEs.
No exploitation is confirmed for the CVEs in this update and the EPSS exploitation probability is currently 3.2%. That can change: CVEs from past updates regularly get exploited months later, which is why deploying on your normal cadence, without exceptions that linger, is what keeps this one boring.
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.
Updated July 24, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Download KB5099539
Get the official update for KB5099539. The download and file size for each supported product are on the Microsoft Update Catalog page.
Update summary
Senserva AI Opinion for KB5099539
KB5099539 is a July 2026 Patch Tuesday Security Update for Windows 10 versions 21H2 and 22H2 across 32-bit, x64, and ARM64 systems, and it addresses CVE-2026-50661, a publicly disclosed BitLocker zero-day. Because the flaw is in BitLocker, any of these Windows 10 devices relying on BitLocker for drive encryption, particularly laptops that can be physically accessed or stolen, are the ones most at risk. Per-update CVE detail is still provisional from the MSRC release document, but the public disclosure of the BitLocker issue raises the urgency for encrypted endpoints.
Do this: Deploy KB5099539 to your Windows 10 21H2 and 22H2 fleet now, starting with BitLocker-protected laptops and other physically exposed devices.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5099539
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5099539
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 313 CVEs. Most severe CVSS 9.9 (Critical). EPSS exploit probability up to 3.2%.
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 KB5099539 is missing on your devices.
Check if KB5099539 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 KB5099539 (checked 2026-07-21). Verify against the article before acting.
We are currently not aware of any issues with this update
Applies to: Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021
Important
Use EKB KB5003791 to update to Windows 10, version 21H2 on supported editions.
This security update includes fixes and quality improvements that are part of the following updates:
June 9,2026—KB5094127 (OS Builds 19045.7411 and 19044.7411)
The following is a summary of the issues that this update addresses when you install this update. If there are new features, it lists them as well. The bold text within the brackets indicates the item or area of the change we are documenting.
[OLE Automation (known issue)] Fixed: Addresses a compatibility issue in OLE Automation (oleaut32.dll) that was introduced by the June 2026 security update. Some applications that use the IDispatch::Invoke method to call COM methods with BYREF parameters that share the same underlying storage might fail. These failures can include parameter marshaling errors or automation call failures. This update corrects how parameter ownership is managed and restores expected application behavior.
[File Explorer (known issue)] Fixed: An issue where the OneDrive shortcut in File Explorer stops working when File Explorer is run with administrative mode.
[Recycle Bin (known issue)] Fixed: This update addresses an issue where the confirmation dialog might display an ...
Writing about KB5099539? 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.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2026-33842 | Critical | 9.9 | 7.5% | No |
| CVE-2026-34328 | Critical | 9.9 | 7.5% | No |
| CVE-2026-34346 | Critical | 9.9 | 7.5% | No |
| CVE-2026-34348 | Critical | 9.9 | 7.5% | No |
| CVE-2026-34349 | Critical | 9.9 | 7.5% | No |
| CVE-2026-40378 | Critical | 9.9 | 48% | No |
| CVE-2026-40400 | Critical | 9.9 | 7.5% | No |
| CVE-2026-40422 | Critical | 9.9 | 7.5% | No |
| CVE-2026-41087 | Critical | 9.9 | 7.5% | No |
| CVE-2026-42900 | Critical | 9.9 | 7.5% | No |
| CVE-2026-42975 | Critical | 9.9 | 7.5% | No |
| CVE-2026-42982 | Critical | 9.9 | 48% | No |
| CVE-2026-42990 | Critical | 9.9 | 48% | No |
| CVE-2026-44806 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49164 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49165 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49167 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49168 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49170 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49171 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49172 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49174 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49175 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49176 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49177 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49178 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49180 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49183 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49184 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49783 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49784 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49787 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49788 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49789 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49790 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49791 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49792 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49793 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49794 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49795 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49796 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49797 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49798 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49799 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49800 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49801 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49803 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49804 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49805 | Critical | 9.9 | 7.5% | No |
| CVE-2026-49807 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50293 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50294 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50296 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50297 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50298 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50299 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50300 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50302 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50303 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50306 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50307 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50308 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50309 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50310 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50311 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50312 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50313 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50316 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50318 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50321 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50325 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50326 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50329 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50330 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50331 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50332 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50333 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50334 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50335 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50337 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50339 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50341 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50343 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50344 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50346 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50347 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50348 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50350 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50351 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50352 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50354 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50356 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50357 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50358 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50359 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50360 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50362 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50363 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50364 | Critical | 9.9 | 3.2% | No |
| CVE-2026-50365 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50366 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50367 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50369 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50371 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50372 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50373 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50374 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50375 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50376 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50377 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50378 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50380 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50381 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50382 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50383 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50384 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50386 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50387 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50388 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50389 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50390 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50391 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50394 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50397 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50399 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50400 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50401 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50402 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50405 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50406 | Critical | 9.9 | 3.2% | No |
| CVE-2026-50407 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50409 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50410 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50411 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50412 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50415 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50417 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50419 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50421 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50422 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50423 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50425 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50427 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50429 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50430 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50431 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50432 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50433 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50434 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50435 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50437 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50439 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50441 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50442 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50445 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50447 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50448 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50449 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50450 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50451 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50452 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50453 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50455 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50456 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50457 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50459 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50460 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50461 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50462 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50463 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50469 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50470 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50471 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50473 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50474 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50475 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50476 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50477 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50478 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50479 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50482 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50484 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50485 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50486 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50489 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50490 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50491 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50492 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50493 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50494 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50495 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50496 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50497 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50498 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50499 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50500 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50502 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50504 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50505 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50509 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50647 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50655 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50661 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50666 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50667 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50668 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50669 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50670 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50672 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50673 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50680 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50681 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50682 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50686 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50688 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50689 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50690 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50692 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50694 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50695 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50696 | Critical | 9.9 | 7.5% | No |
| CVE-2026-50697 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54107 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54109 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54112 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54114 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54115 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54119 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54122 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54124 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54125 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54126 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54128 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54129 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54132 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54982 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54983 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54986 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54987 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54989 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54992 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54993 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54995 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54997 | Critical | 9.9 | 7.5% | No |
| CVE-2026-54999 | Critical | 9.9 | 7.5% | No |
| CVE-2026-55003 | Critical | 9.9 | 7.5% | No |
| CVE-2026-55004 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56168 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56173 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56175 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56176 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56182 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56184 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56186 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56188 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56189 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56190 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56194 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56643 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56644 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56647 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56648 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56649 | Critical | 9.9 | 7.5% | No |
| CVE-2026-56650 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57083 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57084 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57085 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57087 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57089 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57090 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57091 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57092 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57093 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57094 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57095 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57096 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57097 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57976 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57979 | Critical | 9.9 | 7.5% | No |
| CVE-2026-57982 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58526 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58528 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58530 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58531 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58532 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58533 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58534 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58535 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58536 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58538 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58539 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58540 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58541 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58545 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58546 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58547 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58594 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58598 | Critical | 9.9 | 3.2% | No |
| CVE-2026-58601 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58608 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58609 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58610 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58613 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58614 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58619 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58626 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58628 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58629 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58632 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58635 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58637 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58638 | Critical | 9.9 | 7.5% | No |
| CVE-2026-58640 | Critical | 9.9 | 7.5% | No |
What the press says about this update
Trusted-source coverage of the CVEs this update fixes, pulled live from their own feeds.
Affected products
Also released in July 2026
The highest-risk updates from the same release:
The full month, summarized: Microsoft Patch Tuesday.
How to install KB5099539
Any of these paths delivers KB5099539; 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 KB5099539 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 KB5099539, ranked by exploitation.
Common questions about KB5099539
Does KB5099539 have known issues?
Yes. Microsoft's support article documents known issues for KB5099539 (checked 2026-07-21). The Known issues section on this page quotes it; verify against the article before acting.
Is KB5099539 urgent?
KB5099539 is rated Critical with a maximum CVSS of 9.9. No active exploitation is confirmed yet, so schedule it in your prompt patch cycle.
How do I download KB5099539?
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 KB5099539 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 KB5099539?
Yes. This page includes a free, ready-to-paste AI prompt containing KB5099539'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).
Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.