Microsoft’s July 2026 Patch Tuesday release addresses 622 vulnerabilities in a single update—a volume that cybersecurity firm CrowdStrike estimates is five times larger than the count from May. Of these vulnerabilities, two have already been exploited, affecting Active Directory Federation Services and SharePoint Server, while a third related to BitLocker disk encryption remains unpatched despite being publicly disclosed.
Among the 622 vulnerabilities, 255 are related to privilege escalation, making up 41% of the batch. Remote code execution accounts for 166 vulnerabilities (27%), and information disclosure represents 109 vulnerabilities (18%). Windows is the primary focus of these patches, with 413 entries, followed by extended security updates at 335 and the Office suite with 95 entries; many vulnerabilities can affect multiple products simultaneously. The 62 vulnerabilities designated as critical include issues in Windows DHCP service, SharePoint Server, Exchange, SQL Server, Office, and Windows Media Foundation.
As of the bulletin’s publication, two vulnerabilities are already being exploited. CVE-2026-56155 allows for privilege escalation in Active Directory Federation Services, scoring 7.8 on the CVSS scale. Meanwhile, CVE-2026-56164 enables privilege escalation in SharePoint Server with a score of 5.3. A third vulnerability, CVE-2026-50661, which allows bypassing BitLocker’s disk encryption and has a score of 6.1, has been publicly disclosed without an accompanying patch.
Fast-Paced Correction Cycle Since Spring
The last three patch cycles highlight a significant upward trajectory. The May patch batch included approximately 120 fixes, June saw around 200, and July presents a staggering increase with over three times that amount. CrowdStrike attributes this acceleration to various factors, including the expansion of Windows and Office application scope into artificial intelligence functions, the continuous integration of third-party components into identity and collaboration management tools, and strengthened internal detection efforts that identify more vulnerabilities before they can be widely exploited.
This increase in volume presents a challenge for security teams, who face the dilemma of sorting through a much larger number of patches. A cycle of 622 fixes cannot be managed in the same way as a cycle of 120, especially within similar testing and deployment windows. Organizations that adhered to a monthly patching strategy without differentiating between actively exploited vulnerabilities and those that are merely cataloged are at an automatic disadvantage as soon as the bulletin is published.
Two Exploited Vulnerabilities Demand Immediate Attention
Both ADFS and SharePoint Server share a critical trait that heightens risk—they serve as authentication pivots for many internal and external applications. A privilege escalation in ADFS can open access to all federated services that rely on this component for single sign-on, greatly amplifying the potential impact of an initial compromise. IT Social previously reported an incident where a SharePoint Server vulnerability was exploited as an entry point for a ransomware deployment, transitioning from initial access to complete compromise in a matter of hours.
The CVSS score of the SharePoint vulnerability, at 5.3, would categorize it as a moderate priority under a traditional interpretation that ignores active exploitation. This is precisely what known exploitation repositories, like CISA’s KEV catalog, aim to address, by centering real-world exploitation in prioritization over merely technical scoring. For both the ADFS and SharePoint vulnerabilities, remediation should take precedence over the displayed scores.
Unpatched BitLocker Vulnerability Creates Ongoing Risk
CVE-2026-50661 stands apart from the previous vulnerabilities due to its status; it is publicly known but lacks a patch from Microsoft within this cycle. This bypass affects BitLocker’s disk encryption, a safeguard specifically designed to counter unauthorized access to a lost or stolen workstation. An attacker with physical access to the machine could theoretically exploit this vulnerability before a fix is made available.
The public disclosure without an available patch replicates scenarios the industry has seen unfold swiftly before. Citrix, for instance, patched a critical vulnerability in its NetScaler appliances after it had already been exploited less than 24 hours following its disclosure. While there is no indication that CVE-2026-50661 will experience a similar fate, the timeline from public information to a functional proof of concept is now measured in hours rather than weeks, significantly narrowing the window for teams to implement alternative risk mitigation measures in the absence of a patch.
Implications of This Volume for Security Teams
A patch cycle of this magnitude makes the mechanical application of a patch management strategy based solely on a monthly calendar untenable. Teams that rank vulnerabilities strictly by raw CVSS score would allow the SharePoint vulnerability, rated at 5.3, to lag behind less urgent but better-rated patches for several weeks. Real-world exploitation prioritization, driven by known vulnerability catalogs, becomes the default methodology rather than an option for the most mature organizations.
For the BitLocker vulnerability, the absence of a patch does not excuse inaction. Enhanced controls on physical access to workstations, verification of Trusted Platform Module configurations, and increased monitoring of boot-time authentication attempts are available risk mitigation measures prior to a patch’s release. The list of three priorities—ADFS, SharePoint, and BitLocker—is concise, yet implementing these actions across thousands of workstations and servers cannot be completed within the month leading up to the next Patch Tuesday.



