Patch Tuesday

Winsage
January 15, 2026
Microsoft and the U.S. government have issued a warning about a vulnerability in Windows, designated CVE-2026-20805, which is currently being exploited. This flaw allows an authorized attacker to leak a memory address from a remote ALPC port, potentially leading to arbitrary code execution. It has a medium severity rating of 5.5 on the CVSS scale. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added this vulnerability to its Known Exploited Vulnerabilities catalog and requires federal agencies to implement a patch by February 3. Additionally, two other vulnerabilities were acknowledged: CVE-2026-21265, a secure boot certificate expiration bypass with a CVSS rating of 6.4, and CVE-2023-31096, an elevation of privilege flaw affecting third-party Agere Modem drivers, rated at 7.8. Two more vulnerabilities, CVE-2026-20952 (CVSS 7.7) and CVE-2026-20953 (CVSS 7.4), are use-after-free flaws in Office that could allow unauthorized code execution.
Winsage
January 14, 2026
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a Microsoft Windows vulnerability, CVE-2026-20805, to its Known Exploited Vulnerabilities (KEV) catalog, with a CVSS score of 8.7. This vulnerability, part of the January 2026 Patch Tuesday updates, affects the Windows Desktop Window Manager and allows attackers to leak memory information, potentially aiding in further exploits. Federal Civilian Executive Branch agencies must address this vulnerability by February 3, 2026, as mandated by Binding Operational Directive 22-01.
Winsage
January 14, 2026
On Tuesday, Microsoft released its first security update for 2026, addressing 114 vulnerabilities, including eight classified as Critical and 106 as Important. The vulnerabilities include 58 related to privilege escalation, 22 concerning information disclosure, 21 linked to remote code execution, and five categorized as spoofing flaws. A notable vulnerability, CVE-2026-20805, involves information disclosure within the Desktop Window Manager (DWM) and has a CVSS score of 5.5. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added this flaw to its Known Exploited Vulnerabilities catalog, requiring federal agencies to implement fixes by February 3, 2026. Additionally, Microsoft announced the expiration of three Windows Secure Boot certificates issued in 2011, effective June 2026, urging customers to transition to newer certificates to avoid disruptions. The update also removed vulnerable Agere Soft Modem drivers due to a local privilege escalation flaw (CVE-2023-31096) and addressed another critical privilege escalation flaw in Windows Virtualization-Based Security (CVE-2026-20876) with a CVSS score of 6.7. Other vendors, including Adobe, Amazon Web Services, and Cisco, have also released security patches for various vulnerabilities.
Winsage
January 13, 2026
Microsoft's January 2026 Patch Tuesday update, KB5074109, addresses 114 vulnerabilities, including a critical zero-day vulnerability (CVE-2026-20805) in the Windows Desktop Window Manager (DWM) that has been actively exploited. The update is applicable to Windows 11 versions 24H2 and 25H2 and includes security enhancements and updates to AI components. Other high-severity vulnerabilities addressed include CVE-2026-20816 (privilege escalation in Windows Installer), CVE-2026-20817 (elevation of privilege in Windows Error Reporting), CVE-2026-20840 (vulnerability in Windows NTFS), CVE-2026-20843 (flaw in Routing and Remote Access Service), CVE-2026-20860 (vulnerability in Ancillary Function Driver for WinSock), and CVE-2026-20871 (another DWM vulnerability). The update removes legacy modem drivers to minimize the attack surface and resolves reliability issues in Azure Virtual Desktop and WSL networking. It also changes the default setting for Windows Deployment Services (WDS) to disable hands-free deployment. Users can install the update through Windows Update, and a system reboot is required for full application.
Winsage
January 11, 2026
Microsoft is testing a new policy that allows IT administrators to completely uninstall its Copilot AI assistant from managed Windows devices. This policy, named “RemoveMicrosoftCopilotApp,” is being deployed through management tools like Intune and System Center Configuration Manager (SCCM) and addresses concerns about data privacy, resource consumption, and unwanted software in commercial settings. The feature is currently available in Windows 11 Insider Preview Build 26220.7535 (KB5072046) and reflects feedback from IT professionals who prefer controlled environments. While this option is exclusive to enterprise-tier Microsoft 365 subscribers, smaller businesses and individual users have limited options for removal. The policy aims to balance innovation with risk management, especially in regulated sectors like healthcare and finance, where data privacy is critical.
Winsage
January 6, 2026
Microsoft has released a support document titled “Release information for AI components” that details the AI components integrated into Windows 11, which can be installed through Windows Update or accessed via the Microsoft Update Catalog. These components are essential for enabling various AI models to operate locally on devices, and installations typically occur automatically on compatible PCs with 40+ TOPs of NPU. The size of Windows 11 Patch Tuesday updates has increased significantly, now ranging from 4-5GB, compared to previous updates that were under 800MB. Users can manage AI components through Settings > System > AI Components, although this page is empty for older PCs. The changelog includes individual components like the Settings Model, Image Search, Semantic Analysis, and Content Extraction, as well as lower-level elements such as Execution Provider. Updates for these AI models occur every few weeks, often without visible changes.
Winsage
December 30, 2025
Microsoft is modifying core system settings for Windows 11 versions 24H2 and 25H2 by enabling the AppX Deployment Service (Appxsvc) to launch automatically upon boot-up, transitioning from a manual trigger system. This change was confirmed in the December 2025 "Patch Tuesday" update (KB5072033) for both Windows 11 and Windows Server 2025. The Appxsvc will now remain active in the background from the moment the computer powers on, regardless of Microsoft Store access, to enhance system stability and minimize app installation failures or update glitches. Microsoft warns against manually reverting this setting, as it could lead to malfunctions in Store apps and essential services. Analysts suggest this move aligns with a strategy for updating Microsoft Store apps directly through Windows Update.
Winsage
December 19, 2025
Microsoft released an out-of-band update (KB5074976) on December 19 to address Message Queuing (MSMQ) errors caused by December 2025 security updates. These updates have led to operational disruptions in business applications and IIS websites, particularly on systems running Windows 10 22H2, Windows Server 2019, and Windows Server 2016, which received updates KB5071546, KB5071544, and KB5071543. Users reported issues such as inactive MSMQ queues, IIS sites generating "insufficient resources" error messages, and applications unable to write messages to queues. The problems stem from modifications in the MSMQ security model, which altered permissions for the system folder C:WindowsSystem32msmqstorage, requiring MSMQ users to have write access typically reserved for administrators. Systems with full administrative rights do not experience these issues. Microsoft is investigating the matter but has not provided a timeline for a resolution.
Winsage
December 17, 2025
Microsoft has informed the business community about a known issue with Message Queuing (MSMQ) affecting enterprise applications and Internet Information Services (IIS) sites. This problem primarily impacts users on Windows 10 22H2, Windows Server 2019, and Windows Server 2016 who installed specific security updates (KB5071546, KB5071544, and KB5071543) released in December 2025. Symptoms include inactive MSMQ queues, applications unable to write to queues, IIS sites failing with "insufficient resources" errors, and misleading messages about disk space or memory. The issue stems from changes to the MSMQ security model that altered permissions on the C:WindowsSystem32MSMQstorage folder, requiring MSMQ users to have write access to a directory typically restricted to administrators. Microsoft has not provided a timeline for a fix and suggests affected IT administrators contact their support team for temporary workarounds or consider rolling back the updates.
Search