Microsoft Patches Record 570 Windows Vulnerabilities in July Update, Including Three Actively Exploited Zero-Days
Microsoft has issued its largest monthly security update yet, releasing patches for a record 570 vulnerabilities across Windows and associated products. The July Patch Tuesday rollout includes three zero-day flaws, two of which were already being actively exploited in real attacks.
Fifty-nine of the issues received a critical severity rating. Of these, 48 allow remote code execution, nine enable privilege escalation, and the remainder involve security feature bypass or data tampering. The largest category of fixes addressed privilege escalation vulnerabilities, totaling 254, followed by 145 remote code execution flaws, 102 information disclosure issues, 35 denial-of-service problems, and 16 spoofing vulnerabilities.
The first actively exploited zero-day, CVE-2026-56155, affects Active Directory Federation Services. An authenticated attacker can abuse the flaw to obtain administrative privileges. Microsoft has not yet disclosed technical details of the observed attacks.
The second zero-day, CVE-2026-56164, resides in SharePoint Server. Due to missing authentication checks, a remote attacker can elevate privileges. As a temporary mitigation, Microsoft recommends enabling AMSI and full request-body scanning.
The third zero-day, CVE-2026-50661, was already publicly known before the update. It allows an attacker with physical access to bypass BitLocker encryption and access protected data. Microsoft had previously warned that the volume of patches would increase because the company is now using AI to hunt for vulnerabilities in the Windows source code.
The update touches numerous components, including multiple versions of .NET and .NET Framework, Active Directory Certificate Services, Active Directory Domain Services, Active Directory Federation Services, Azure Active Directory, Microsoft Office and Excel, Microsoft Defender, Exchange Server, and various Azure services. A selection of the addressed CVEs includes:
- .NET – CVE-2026-50649 (Remote Code Execution, Important), CVE-2026-50525 (Denial of Service, Important)
- Active Directory Federation Services – CVE-2026-56155 (Elevation of Privilege, Important)
- Microsoft Office – CVE-2026-55129, CVE-2026-55049, CVE-2026-55045 (Remote Code Execution, Critical)
- Microsoft Defender – CVE-2026-55012, CVE-2026-55011 (Remote Code Execution, Critical)
Security teams are strongly encouraged to deploy the updates as soon as possible to reduce exposure to both known and newly discovered threats.
Related articles
Browser Built on Mistakes: How Real-World Attacks Shaped Modern Browser Defenses
Browser security features such as process isolation, sandboxing, and restrictions on code execution were not designed in isolation but evolved directly in response to concrete attacks over more than a decade. Early threats like malicious Flash advertisements in 2015 demonstrated how a single compromised banner could compromise an entire system, prompting the industry to phase out plugins entirely. Later discoveries, including the Spectre vulnerability, forced browsers to implement stricter site isolation and timing-attack mitigations that remain in place today. Session hijacking and malicious browser extensions further drove the adoption of stronger cookie protections and permission models. BI.ZONE analysts trace this history through specific incidents to show why current architectures prioritize separation of sites into distinct processes. The resulting design reduces the blast radius of any single exploit and continues to adapt as new attack classes emerge.
cKEV Index Launches to Prioritize Vulnerabilities as AI Accelerates Exploit Development
CyberOK has introduced the open cKEV Index, a catalog of high-priority vulnerabilities ranked by the Urgent Patch Score (UPS) methodology. The index incorporates timelines of events such as exploit publication, proof-of-concept releases, and confirmed attacks to help organizations prioritize patching under resource constraints. It addresses the growing gap between rapid AI-assisted vulnerability discovery and slower remediation processes at both vendors and customers. Examples from Anthropic reports highlight how threat actors used AI agents for reconnaissance, code analysis, and exploit development against Android apps and web applications. Microsoft and Oracle have publicly linked increased vulnerability findings and larger patch releases to AI tooling. The UPS framework defines progressive phases from Radar to Emergency/IR, allowing teams to act on strong signals without waiting for full confirmation. An open version of the catalog is now available with detailed event histories for Urgent Patch and Emergency stages.
Apache HTTP Server 2.4.69 Patches 20 Vulnerabilities Including CVSS 9.8 Issues
The Apache HTTP Server development team released version 2.4.69 on October 1, 2026, addressing a total of 20 vulnerabilities. While the Apache Security Team assessed most issues as moderate or low in impact, several vulnerabilities received CVSS base scores as high as 9.8. The update includes fixes for stack-based buffer overflows, use-after-free conditions, and out-of-bounds writes affecting multiple modules. No vulnerabilities were rated Critical or Important by the developers, with five classified as Moderate and fifteen as Low. Specific fixes cover the mod_vhost_alias, mod_http2, mod_dav, and mod_dav_fs modules, along with Windows-specific path handling problems.
BrokenPipe PoC Exploits Steam Client Service for Silent SYSTEM Privilege Escalation on Windows
A new proof-of-concept named BrokenPipe demonstrates how a standard Windows user can escalate privileges to NT AUTHORITY\SYSTEM through the Steam Client Service without requiring administrator credentials or triggering a UAC prompt. The vulnerability stems from insufficient signature validation in VDF installation scripts processed by steamservice.exe, allowing an attacker to control the execution path of a malicious script. The issue affects Steam version 10.96.30.42 on both Windows 10 and Windows 11, though no public CVE has been assigned yet. Valve was notified of the flaw in March, several months prior to public disclosure. The attack is strictly local and requires initial code execution under a standard user account, making it relevant for shared or corporate environments. Security teams are advised to inventory Steam installations, apply application allowlisting, and monitor for anomalous SYSTEM-level processes linked to the service while awaiting an official patch.