A June entry on CISA's must-fix list is climbing our search rankings again, with ransomware crews attached to it. And Microsoft's November update, clean for two days, picked up its first two known issues overnight: one for bulk Windows activation, one for installing the update at all.
The PeopleSoft flaw everyone is searching for again
CVE-2026-35273 in Oracle PeopleSoft Enterprise PeopleTools is a missing-authentication flaw rated Critical severity at CVSS 9.8: a critical function that never asks who you are. CISA added it to the Known Exploited Vulnerabilities catalog on June 12 with a June 15 due date, the same three-day fuse Barracuda just got, and the catalog flags it for known ransomware campaign use. Five months later it sits at number five on our hot ranking, pushed there by search demand, and FIRST's Exploit Prediction Scoring System scores it at 96.7 percent. PeopleSoft runs HR, payroll, finance and student systems, so if it is in your environment, confirm the June remediation is applied rather than assuming it.
Smart App Control works again
Microsoft's notes on the October Windows 11 update KB5127648, revised Wednesday, close out the "You might be unable to turn on Smart App Control" issue: "This issue was resolved for Windows 11, versions 26H2 and 25H2, by Windows updates released on and after October 28, 2026 (KB5127936)" and "for Windows 11, version 24H2, by Windows updates released on or after November 10, 2026", which is KB5132061. The same night's notes mark the last symptoms of the September USB Audio Class 1.0 problem addressed, in KB5132061 on the client side and KB5131080 on Windows Server 2025.
November's update can break slmgr activation commands
Overnight, Microsoft added a new known issue to five November updates: "Windows activation and licensing commands might fail with error 0x80041008." After installing the update, Software Licensing Management Tool operations, including slmgr.vbs /skms-domain and slmgr.vbs /ipk, can fail with "0x80041008, Invalid parameter (SWbemObjectEx)." Microsoft says it "primarily affects organizations that use command-line tools or automated processes to manage Windows activation and licensing", and that "Devices that are already activated remain activated." Machines being set up for KMS activation are the ones that hit it. A workaround is available through Microsoft Support for business, and Microsoft says it is "working on a resolution that will be available in the coming days." Listed on KB5131080 (Windows Server 2025), KB5131090 (Windows Server 2022), KB5131087 (Windows 11 23H2), KB5131096 (Windows 10 21H2 and 22H2) and KB5131085 (Windows 10 1809 and Windows Server 2019).
The install watch caught one: a self-repairing failure
The second overnight entry sits on KB5132061, the November update for Windows 11 24H2, 25H2 and 26H2: some devices "might repeatedly attempt to install the update or display error code 0x80070306, 0x800f0989, or 0x800f0993." No hands-on fix is asked for. The repair is rolling out automatically to affected internet-connected devices that update through Windows Update, and Microsoft says "All affected devices should be repaired in 24 to 48 hours starting from November 11, 2026, 10am PT." That window closes at 10 AM Pacific today, so a machine still refusing the November update after this afternoon is the one to escalate: Microsoft's guidance at that point is to contact Microsoft Support.
Deadline day for Barracuda
The two exploited Barracuda flaws CISA put on a three-day clock are due today, November 13: CVE-2026-111560, an OS command injection across multiple Barracuda products, and CVE-2026-116606, an authentication bypass in the Email Security Gateway. The rest of Tuesday's additions are due November 24: CVE-2026-125350 in Google Chromium, CVE-2026-124194 in Microsoft Outlook, CVE-2026-111793 in Openwave Webtop, and CVE-2026-20320 in Cisco BroadWorks, the platform behind many hosted business calling services and itself moving up our search data this week. The deadlines bind federal agencies; everyone else gets a dated to-do list for free.
If you do three things this week
- Ask whether the June fix for the PeopleSoft flaw is actually applied; CISA flags it for ransomware use and the search interest says it is anything but old news.
- Tell whoever images machines about the slmgr error 0x80041008 before Monday's builds, and keep November's updates rolling everywhere else; already-activated devices are unaffected.
- Confirm Barracuda patches today, and escalate any Windows 11 machine that still will not take the November update after this afternoon.
Clay in the Morning is Senserva's weekday patch and security show; this is its written companion. The sources behind our trackers, and their terms, are on our Data sources & thanks page.