All posts

Busy Patch Monday: Windows Activation, Exchange, an Exploited Chrome and Edge Flaw, and Apache

Senserva Watch

Join Senserva Watch and get Three Free Unlimited Audits with our full Claude MCP, a fresh audit credit every quarter, alerts when a CVE or KB you follow changes, critical security updates when they land, the Patch Tuesday wire on release day, and 20% off when you buy.

Join Senserva Watch

One email address. No tenant connection, no agent, no call.

Four patch items for November 16, 2026: Windows Server activation, Exchange sign-ins, an exploited Chrome and Edge flaw, and Apache HTTP/2

Mondays after Patch Tuesday are usually quiet. This one is not. Four patch items are worth your time this week: two Microsoft fixes for problems the updates themselves caused, an actively exploited browser flaw that reaches Microsoft Edge as well as Chrome, and a critical bug in Apache HTTP Server. Microsoft comes first.

1. Windows Server activation fails after the November update, and the fix is out

Microsoft's release notes for KB5131080 (Windows Server 2025, our page: KB5131080) and KB5131090 (Windows Server 2022, our page: KB5131090) list a known issue: after the November update, running slmgr.vbs /skms-domain or slmgr.vbs /ipk can fail with "error 0x80041008, Invalid parameter (SWbemObjectEx)". Microsoft says devices that are already activated remain activated, and devices with the KMS client key already in their image that do not use slmgr for further configuration are unaffected.

Microsoft says the issue "is resolved in Windows updates released on and after November 13, 2026": the out-of-band updates KB5136489 for Windows Server 2025 and KB5136487 for Windows Server 2022. We do not have pages for those two out-of-band updates yet, so the links go to Microsoft's release notes. BleepingComputer reports that Windows 10 21H2/22H2, Windows 11 23H2 and Windows Server 2019 are affected too; check Windows release health for your version.

2. Exchange Server sign-ins broken by October's Windows Server updates, fixed in November

The Exchange Team blog says the October 2026 Windows Server updates can make Exchange 2016, 2019 and Subscription Edition servers unstable. Microsoft's release notes for KB5131080 and KB5131090 say the November update fixes an issue that "might prevent signing in to Outlook on the web (OWA), cause email messages to remain in the Outlook Outbox without being delivered, or prevent Exchange from accessing mailboxes during mailbox replication." The Exchange Team's guidance is short: "Please install November 2026 (or newer) updates for Windows Server." It also says the issues are "not related to installation of any version of Exchange Server updates," so there is no reason to roll back Exchange. The November updates are KB5131080 and KB5131090 on Server 2025 and 2022. BleepingComputer covered the fix on November 11.

3. Exploited Chrome flaw CVE-2026-125350, also fixed in Microsoft Edge

Google's Chrome release notes say: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." The flaw (our page: CVE-2026-125350) is a use-after-free in XML, fixed in Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux. CISA added it to the Known Exploited Vulnerabilities catalog on November 10, with a federal due date of November 24, and notes that it could affect other Chromium browsers, including Microsoft Edge.

That makes it a Microsoft item too. Microsoft's Edge security release notes say Edge Stable 157.0.4341.46, released November 9, "contains a fix for it." Both browsers update themselves, but only after a restart, so check the version on machines that stay open for days. Krebs on Security also notes the bug is being patched in Chromium-based browsers like Edge, and SANS covered it on its November 10 Stormcast, as did BleepingComputer.

4. Apache HTTP Server: critical HTTP/2 flaw CVE-2026-119618

This one matters only if you run Apache. We include it because Senserva Watch covers patches from every vendor. The Apache HTTP Server project's advisory text, as published by NVD, describes CVE-2026-119618 as a flaw in mod_http2 that "can lead to RCE", and BleepingComputer reports that Apache rates it critical. It affects Apache HTTP Server 2.4.55 through 2.4.70 and is fixed in 2.4.71, released November 11. BleepingComputer notes it requires HTTP/2 to be enabled, which is off by default. Apache's advisory makes no exploitation claim, and BleepingComputer reports that Wiz is unaware of any public exploits or attacks so far. We do not have a page for this CVE yet. SANS covered it on its November 12 Stormcast.

What to do this week

  • Windows Server 2025 and 2022 that activate through KMS commands: install KB5136489 or KB5136487.
  • On-premises Exchange: make sure the November Windows Server update is installed on every Exchange server.
  • Chrome and Edge: confirm 157.0.8103.50 or later for Chrome and 157.0.4341.46 or later for Edge, and restart browsers that have been open for days.
  • Apache with HTTP/2: move to 2.4.71.

Senserva Watch sends updates like these by email. Microsoft, Google, CISA and the Apache project are the sources; we track and share them.

Sources

All posts