Microsoft Releases Record 966 Patches in Largest Patch Tuesday Ever, Including Two Actively Exploited Zero-Days
Microsoft has delivered its largest-ever monthly security update, releasing patches for a record 966 vulnerabilities in the September Patch Tuesday cycle. This marks the biggest single-month fix count in the company's history and significantly exceeds the 570 issues addressed in July and the 400 resolved in August.
The update closes two actively exploited zero-day vulnerabilities. The first, CVE-2026-81963, resides in the Windows Update stack and stems from improper link handling. An authenticated local attacker could leverage it to escalate privileges to SYSTEM level. The second zero-day, CVE-2026-85880, affects the Windows ALPC mechanism through a buffer overflow that similarly grants attackers SYSTEM privileges. Microsoft has not disclosed details on the attack campaigns or the threat actors behind the exploitation.
Of the total fixes, 105 vulnerabilities carry a critical severity rating. The largest categories are privilege-escalation issues (438) and remote-code-execution flaws (258). Additional problems allow security-feature bypasses, information disclosure, denial-of-service conditions, and data tampering.
The 966 patches do not include another 204 vulnerabilities fixed earlier in September in products such as Azure, Copilot Studio, Entra ID, Edge, Microsoft Fabric, and Power Automate. The sharp increase in volume aligns with Microsoft's recent adoption of an AI-powered system designed to identify security bugs in its own software.
Selected Patched Vulnerabilities
- .NET – Multiple Elevation of Privilege and Information Disclosure issues (CVE-2026-69805, CVE-2026-58649, CVE-2026-69806)
- Active Directory Certificate Services (AD CS) – Several Elevation of Privilege and Tampering vulnerabilities (CVE-2026-69821, CVE-2026-69624)
- Azure AI Language and Azure Cosmos DB – Critical Elevation of Privilege and Spoofing flaws
- Graphic Fonts – Critical Remote Code Execution vulnerabilities (CVE-2026-72986, CVE-2026-73018)
Administrators are strongly advised to apply the updates immediately, especially on systems exposed to the internet or handling sensitive workloads.
Related articles
Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison
An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.
VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server
Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.
September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication
The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.
API Token Lifecycle: From Issuance to Revocation and Secure Management
The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.