Microsoft July 2026 Patch Tuesday: ​
621 CVEs and Critical Elevation of Privilege Vulnerabilities

Stay ahead of critical vulnerabilities with our breakdown of this month's Microsoft security patches.

Release Date: Tuesday, July 14, 2026
Release Time: 10:00 AM PST / 1:00 PM EST / 6:00 PM UTC
Status: Released
Last Updated: July 14, 2026


Executive Summary: Record-Breaking 621 CVE Release

Microsoft has released its July 2026 Patch Tuesday security updates, addressing 621 unique Microsoft CVEs with 1,149 total vulnerabilities when including updates to existing CVEs and related entries. This is the largest single Patch Tuesday release in 2026, significantly exceeding June's 200-vulnerability record.

Release Statistics:

  • 621 Microsoft CVEs addressed
  • 1,149 total vulnerabilities (includes updates to existing CVEs and related entries)
  • 62 Critical-severity vulnerabilities requiring immediate deployment
  • 552 Important-severity vulnerabilities requiring priority deployment
  • 6 Moderate-severity vulnerabilities
  • 1 Low-severity vulnerability

Critical Vulnerabilities Requiring Immediate Attention:

  • CVE-2026-50661: Windows BitLocker Security Feature Bypass Vulnerability
  • CVE-2026-56155: Active Directory Federation Services (ADFS) Elevation of Privilege Vulnerability
  • CVE-2026-56155: Microsoft SharePoint Server Elevation of Privilege Vulnerability

IMMEDIATE ACTIONS REQUIRED:

  • Deploy critical-severity patches within 24-48 hours
  • Prioritize CVE-2026-50661 (BitLocker bypass) for encrypted systems
  • Prioritize CVE-2026-56155 (ADFS and SharePoint EoP) for domain environments
  • Complete Kerberos RC4 hardening remediation
  • Test authentication and encryption infrastructure before production deployment
  • Implement comprehensive vulnerability scanning to verify patch deployment

July 2026 Patch Tuesday: Scale and Scope

621 CVEs and 1,149 Total Vulnerabilities: Largest Release of 2026

The July 2026 Patch Tuesday release represents unprecedented scale in Microsoft's monthly security updates:

Volume Context:

The distinction between 621 unique CVEs and 1,149 total vulnerabilities reflects how Microsoft tracks security issues:

  • 621 unique CVEs: Individual vulnerability identifiers tracked in Common Vulnerabilities and Exposures
  • 1,149 total vulnerabilities: Includes CVE updates, dependency fixes, and related security issues addressed in the release

Severity Distribution Analysis

Microsoft categorized all 621 CVEs by severity:

Critical-Severity: 62 CVEs (10.0%)

  • Require deployment within 24-48 hours
  • Pose significant compromise risk if unpatched
  • Include elevation of privilege and security feature bypass vulnerabilities
  • Examples: CVE-2026-50661 (BitLocker bypass), CVE-2026-56155 (ADFS/SharePoint EoP)

Important-Severity: 552 CVEs (88.9%)

  • Require deployment within 1-2 weeks
  • Include information disclosure and lower-impact flaws
  • Can be batched with other monthly updates in systematic patch deployment
  • Should not be deferred beyond 2 weeks

Moderate-Severity: 6 CVEs (0.97%)

  • Require routine deployment in normal patch management cycle
  • Can be grouped with monthly updates
  • Acceptable to defer up to 30 days if business critical

Low-Severity: 1 CVE (0.16%)

  • Minimal security impact
  • Can be deferred or bundled with future updates
  • Acceptable to defer beyond monthly cycle

The high proportion of critical-severity vulnerabilities (62 out of 621) means organizations cannot selectively patch. Nearly 10% of this release requires emergency deployment attention.

Critical Vulnerabilities: Priority Deployment

CVE-2026-50661: Windows BitLocker Security Feature Bypass

Severity: Critical
Component: Windows BitLocker Drive Encryption
Impact: Security Feature Bypass allowing unauthorized access to encrypted data
Affected Systems: Windows systems using BitLocker encryption

Deployment Priority: CRITICAL

Organizations using BitLocker for full-disk or data encryption must deploy CVE-2026-50661 within 24-48 hours. This vulnerability affects the security guarantees of encrypted systems and requires immediate remediation.

Action Items:

  • Identify all systems with BitLocker enabled
  • Verify BitLocker recovery keys are accessible before patching
  • Deploy patch to test environment first
  • Monitor for potential boot failures (have BitLocker recovery procedures ready)
  • Deploy to production after successful testing
  • Verify BitLocker remains functional post-patch

CVE-2026-56155: Active Directory Federation Services (ADFS) Elevation of Privilege

Severity: Critical
Component: Active Directory Federation Services (ADFS)
Impact: Elevation of Privilege allowing attackers to gain higher privileges within ADFS environments
Affected Systems: Organizations running ADFS (on-premises or hybrid environments)

Deployment Priority: CRITICAL for Organizations Using ADFS

Active Directory Federation Services handles authentication and authorization in hybrid cloud scenarios. This elevation of privilege vulnerability requires immediate patching for organizations using ADFS.

Action Items:

  • Identify all ADFS servers in on-premises environments
  • Identify hybrid Azure AD Connect environments using ADFS
  • Test patches in staging ADFS environment first
  • Verify authentication flows continue functioning after patch
  • Monitor for authentication failures during production deployment
  • Complete deployment within 24-48 hours

CVE-2026-56155: Microsoft SharePoint Server Elevation of Privilege

Severity: Critical
Component: Microsoft SharePoint Server
Impact: Elevation of Privilege within SharePoint environments
Affected Systems: Organizations running SharePoint Server (2016, 2019, on-premises)

Deployment Priority: CRITICAL for SharePoint Environments

Microsoft SharePoint Server stores critical business documents and data. An elevation of privilege vulnerability allows attackers to gain unauthorized access. Organizations running SharePoint Server must deploy this patch within 24-48 hours.

Action Items:

  • Identify all SharePoint Server deployments (2016, 2019, and later versions)
  • Test patches in non-production SharePoint environments first
  • Verify document access and sharing functionality after patch
  • Monitor for SharePoint service disruptions during deployment
  • Complete deployment within 24-48 hours

Kerberos RC4 Hardening Phase 2: Enforcement Active

Phase 2 Enforcement: RC4 Disabled by Default

July 14, 2026 marks the effective enforcement date for Kerberos RC4 hardening Phase 2. As of this release:

  • RC4 encryption in Kerberos authentication is disabled by default
  • Systems relying on RC4 for domain authentication experience failures
  • Legacy applications cannot authenticate to domain controllers
  • Organizations must have completed RC4 remediation or have emergency workarounds in place

Impact Assessment

Organizations that did not complete RC4 remediation before July 14 are now experiencing:

Authentication Failures:

  • Domain-joined systems failing to authenticate
  • Service accounts unable to renew Kerberos tickets
  • Applications using RC4 for authentication failing to connect
  • Network devices (printers, switches, management interfaces) losing authentication

Event Logging:

  • Event ID 4771: Pre-authentication failed (RC4-related)
  • Event ID 4772: Pre-authentication failure details logged
  • Increased event volume on domain controllers

Emergency Remediation

If You're Experiencing Authentication Failures:

  1. Identify failing system using domain controller event logs:
# Query domain controller for RC4 authentication failures
Get-WinEvent -FilterHashtable @{LogName='Security'; ID=4771} |
Where-Object {$_.Message -match 'Encryption type'} |
Select-Object TimeCreated, @{Name='System';Expression={$_.Properties[0].Value}} |
Sort-Object TimeCreated -Descending
  1. Determine remediation approach for each affected system:

    • Upgrade: Deploy application version supporting AES-based Kerberos
    • Temporary RC4 fallback: Enable RC4 support for specific systems (maximum 30 days)
    • Network isolation: Configure systems to authenticate locally only
    • Hardware replacement: End-of-life systems may require replacement
  2. Implement temporary RC4 fallback only if necessary:

# Temporarily enable RC4 support (emergency only, maximum 30 days)
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters" `
-Name "SupportedEncryptionTypes" -Value 31
# Value 31 enables: AES256_HMAC_SHA1, AES128_HMAC_SHA1, RC4_HMAC, DES_CBC_MD5, DES_CBC_CRC

Important: Temporary RC4 fallback is an emergency measure only. Permanent solution requires upgrading affected systems.

  1. Plan permanent remediation:
    • Contact software vendors for upgrade paths
    • Budget for hardware replacement if necessary
    • Plan network segmentation if no remediation path exists
    • Complete permanent remediation before Phase 3 enforcement (expected 2027)

Affected Products and Components

July 2026 patches affect nearly the entire Microsoft product portfolio:

Operating Systems

  • Windows 11: All versions (21H2 through 26H1)
  • Windows 10: ESU-enrolled systems only (22H2, 21H2)
  • Windows Server: 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, 2025

Productivity and Enterprise Applications

  • Microsoft Office 2021, 2019, 2016
  • Microsoft 365 Apps for Enterprise
  • Microsoft Excel, Word, PowerPoint, Outlook, Access
  • Microsoft Teams
  • Microsoft SharePoint Server 2019, 2016
  • Microsoft Exchange Server 2019, 2016
  • Dynamics 365 (on-premises versions)

Server and Infrastructure

  • SQL Server 2022, 2019, 2017, 2016
  • Hyper-V (all versions)
  • Active Directory Domain Services
  • Active Directory Federation Services (ADFS)
  • Windows Server Update Services (WSUS)
  • Windows DNS Server
  • Internet Information Services (IIS)
  • Remote Desktop Services

Cloud and Azure Services

  • Azure services (multiple components)
  • Azure Kubernetes Service (AKS)
  • Azure SQL Database
  • M365 Copilot and AI services
  • Azure DevOps

Development Tools

  • Visual Studio 2022, 2019
  • Visual Studio Code
  • .NET Framework 4.8, 4.7.2
  • .NET 10.0, 9.0
  • GitHub Copilot integration

Network and Authentication

  • Windows Kerberos authentication mechanism
  • LDAP (Lightweight Directory Access Protocol)
  • Remote Desktop Protocol (RDP)
  • Windows Authentication
  • VPN authentication components

Browser and Edge

Encryption and Security

  • Windows BitLocker Drive Encryption
  • Windows Secure Boot components
  • Cryptographic Services

Additional Components

  • Windows Print Spooler
  • Windows Graphics components
  • Windows Event Logging
  • Windows Telephony Service
  • Windows Storage services

Deployment Strategy and Timeline

Critical (24-48 Hours): CVE-2026-50661 and CVE-2026-56155

Hours 0-4 (Immediate):

  • Download all July patches
  • Identify systems affected by CVE-2026-50661 (BitLocker) and CVE-2026-56155 (ADFS/SharePoint)
  • Activate support staffing
  • Prepare test environments

Hours 4-12 (Pilot Deployment):

  • Deploy CVE-2026-50661 to pilot BitLocker systems
  • Deploy CVE-2026-56155 to pilot ADFS/SharePoint environments
  • Test functionality thoroughly
  • Monitor for issues

Hours 12-24 (Wave 1 Production):

  • Deploy CVE-2026-50661 to non-critical BitLocker systems
  • Deploy CVE-2026-56155 to non-critical ADFS/SharePoint systems
  • Monitor deployment success

Hours 24-48 (Wave 2 Production):

  • Deploy to remaining affected systems
  • Verify patch installation
  • Test functionality

Important (1-2 Weeks): Remaining 60 Critical and 552 Important Patches

Days 2-7:

  • Deploy remaining 60 critical-severity patches
  • Prioritize server infrastructure (Active Directory, Exchange, SQL Server)
  • Systematic deployment to production infrastructure

Days 8-14:

  • Deploy 552 Important-severity patches
  • Phased rollout across all systems
  • Monitor patch success rates
  • Address compatibility issues

Moderate and Low (30 Days): 6 Moderate and 1 Low Severity

  • Deploy as part of regular patch management cycle
  • Can be grouped with future updates
  • No urgency for immediate deployment

Testing Checklist

Before deploying July patches to production, validate:

System Functionality:

  • [ ] Windows boots successfully
  • [ ] Network connectivity functions
  • [ ] Kerberos authentication successful
  • [ ] Remote Desktop Services operational
  • [ ] Print services functional
  • [ ] File sharing working
  • [ ] LDAP queries successful (if used)
  • [ ] VPN authentication operational

BitLocker Validation (for CVE-2026-50661):

  • [ ] BitLocker remains enabled post-patch
  • [ ] Encrypted drives accessible
  • [ ] BitLocker recovery key accessible if needed
  • [ ] No boot failures or BitLocker errors
  • [ ] Status verification: manage-bde.exe -status

ADFS/SharePoint Validation (for CVE-2026-56155):

  • [ ] ADFS authentication flows successful
  • [ ] SharePoint document access functional
  • [ ] User authentication to SharePoint working
  • [ ] Service accounts renewing Kerberos tickets
  • [ ] No authentication errors in logs

Application Compatibility:

  • [ ] Line-of-business applications authenticate to domain
  • [ ] Microsoft Office applications functional
  • [ ] Database applications connecting successfully
  • [ ] Enterprise applications authenticated
  • [ ] Email services (Exchange, Outlook) operational
  • [ ] Custom applications functioning normally

Kerberos and Authentication:

  • [ ] Kerberos ticket generation working
  • [ ] No RC4 errors in event logs
  • [ ] Domain controller authentication functional
  • [ ] Service account authentication successful
  • [ ] Cross-domain authentication working

Performance Verification:

  • [ ] Boot times acceptable
  • [ ] Application launch times normal
  • [ ] Network throughput satisfactory
  • [ ] No unusual resource consumption
  • [ ] Event logs clean (no critical errors)

Third-Party Vendor Coordination

Coordinate with third-party updates released concurrently with Microsoft Patch Tuesday:

  • Adobe: Monthly security updates for Reader, Acrobat, Creative Cloud
  • Google Chrome: Weekly updates addressing discovered vulnerabilities
  • Mozilla Firefox: Monthly security updates for Firefox and Firefox ESR
  • Oracle: Critical Patch Updates for Java SE, Oracle Database
  • SAP: Security Patch Day updates for SAP platforms
  • Cisco, Fortinet, VMware: Network and infrastructure security updates

Resources and Support

Microsoft Official Resources

Zecurit Resources

Vulnerability Intelligence

Conclusion: Largest Release of 2026 Requires Systematic Approach

July 2026 Patch Tuesday establishes a new record with 621 unique Microsoft CVEs and 1,149 total vulnerabilities. The 62 critical-severity flaws, including CVE-2026-50661 (BitLocker bypass) and CVE-2026-56155 (ADFS/SharePoint EoP), require aggressive, immediate deployment.

Critical Action Items:

  1. Deploy CVE-2026-50661 within 24-48 hours (BitLocker systems)
  2. Deploy CVE-2026-56155 within 24-48 hours (ADFS and SharePoint environments)
  3. Deploy remaining 60 critical patches within 48-72 hours
  4. Complete Kerberos RC4 remediation for ongoing authentication failures
  5. Deploy remaining 552 Important patches within 1-2 weeks
  6. Test all patches thoroughly before production deployment
  7. Implement comprehensive vulnerability scanning to verify deployment

The Bottom Line:

July 2026 Patch Tuesday is the largest security release of the year, requiring maximum organizational resources and commitment. The critical vulnerabilities affecting BitLocker encryption and ADFS/SharePoint authentication demand immediate deployment priority. However, the 552 Important-severity patches cannot be overlooked and must be systematically deployed across the enterprise within 1-2 weeks.

Organizations should treat this release with the urgency it deserves while implementing systematic, tested deployment procedures to ensure comprehensive coverage and minimize operational disruption.


For comprehensive endpoint management and automated patch deployment with vulnerability scanning and compliance reporting, explore Zecurit Endpoint Manager.

Patch Tuesday: CVE Details

Below is a detailed list of the security patches and CVEs released in this month's Patch. This information is fetched directly from the Microsoft Security Response Center (MSRC) to help you stay protected with the latest patches.

What is Patch Tuesday and Why is it so Important?

Introduced by Microsoft in 2003, Patch Tuesday was created to bring order to the chaotic world of software updates. Before this schedule, updates were released sporadically, making it difficult for IT teams to plan their patching efforts.

Today, the predictable monthly schedule allows administrators to prepare for the deployment of these patches. However, the importance of Patch Tuesday goes beyond simple scheduling:

  • Proactive Vulnerability Management: It is Microsoft's primary mechanism for addressing publicly known Common Vulnerabilities and Exposures (CVEs) in its products.

  • Averting Cyberattacks: Timely patching is the most effective way to prevent cybercriminals from exploiting known weaknesses. For every patch Microsoft releases, attackers race to reverse-engineer the update to find the underlying vulnerability and develop an exploit for unpatched systems—a phenomenon often referred to as "Exploit Wednesday."

  • System Stability: Beyond security, these updates often contain important bug fixes and performance enhancements that ensure your systems run smoothly.

Patch Management Best Practices for Businesses

Effectively handling Patch Tuesday updates is a core responsibility for any IT team. Simply installing the patches isn't enough; a well-defined process is needed to minimize risk and prevent system downtime.

Here are some best practices for managing your patching cycle:

  1. Prioritize Patches: Not all patches are created equal. Focus on deploying updates with a "Critical" or "Important" severity rating first, as these address the most severe vulnerabilities.

  2. Test Before Deployment: Never roll out patches to your entire organization without testing them first. Use a staging or lab environment that mirrors your production systems to check for any compatibility issues or bugs.

  3. Automate the Process: Tools like Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager (SCCM) are indispensable for automating the deployment of patches. Automation saves time, reduces human error, and ensures consistency across your network.

  4. Monitor and Verify: After deployment, actively monitor systems to ensure the patches were installed correctly and did not cause any unexpected issues. A rollback plan should be in place to quickly revert any problematic updates.

  5. Stay Informed: Follow official Microsoft security channels and industry news to stay up-to-date on any out-of-band updates (critical patches released outside of the normal schedule) or known issues with the monthly patches.

Understanding CVEs: What to Look For

Patch Tuesday updates are tied to specific CVEs. A CVE (Common Vulnerabilities and Exposures) is a unique ID number assigned to a publicly known security flaw. Each CVE entry provides a brief description of the vulnerability, allowing security professionals to track and prioritize fixes.

When reviewing our monthly list of CVEs, pay close attention to:

  • Severity Rating: Microsoft assigns a severity rating (Critical, Important, Moderate, Low) to each vulnerability. Critical vulnerabilities, which could allow remote code execution without user interaction, should be your highest priority.

  • Exploitability: The "Exploited" status indicates if a vulnerability is being actively targeted by attackers. Patches for these CVEs must be applied immediately.

Patch Tuesday is more than just a monthly event; it is the cornerstone of modern vulnerability management for anyone using Microsoft products. By understanding what it is, embracing best practices, and staying informed about the latest CVEs, you can strengthen your security posture and protect your organization from a constantly evolving threat landscape.

Frequently Asked Questions (FAQs)

  • What is Patch Tuesday?

    Patch Tuesday is the second Tuesday of each month when Microsoft releases its regular updates for Windows operating systems and other Microsoft products. These updates typically include security patches, bug fixes, and sometimes feature improvements.

  • Why is Patch Tuesday important?

    Patch Tuesday is crucial for maintaining the security and stability of systems. The updates often address vulnerabilities that could be exploited by attackers, and keeping systems up to date helps protect against these risks.

  • How do I know when a new Patch Tuesday update is released?

    Microsoft releases Patch Tuesday updates on their website and through Windows Update. For detailed patch notes, you can refer to Microsoft's Security Update Guide or subscribe to update notifications from your device or trusted sources like security blogs.

  • Can I manually install Patch Tuesday updates?

    Yes, you can manually download and install updates through Windows Update, or directly from the Microsoft Update Catalog website, which offers patches for individual downloads.

  • Do I need to install every update?

    It’s highly recommended to install all security updates to ensure your system remains protected from known vulnerabilities. However, non-security updates or feature updates might be optional based on your needs.

  • What happens if I miss a Patch Tuesday update?

    If you miss a Patch Tuesday update, it’s important to install the updates as soon as possible to avoid potential security risks. Microsoft allows you to download and install any missed updates through Windows Update.

  • How do I manage Patch Tuesday updates on multiple systems?

    For businesses or IT administrators, you can use Windows Server Update Services (WSUS), System Center Configuration Manager (SCCM), or third-party patch management tools to schedule, approve, and distribute updates across multiple systems.

  • Are all updates released on Patch Tuesday critical?

    Not all updates are critical. Patch Tuesday updates include a range of fixes, from critical security patches to optional non-security updates. It’s important to assess which updates are most relevant to your environment.

  • What is the impact of not applying Patch Tuesday updates?

    Failing to apply updates can leave your system vulnerable to exploits and attacks. Many of the updates address critical security flaws that cybercriminals may target, so staying updated is vital for system security.

Important Links

Microsoft Security Updates Guide
This is the primary source for information on Microsoft's security updates. It includes details on the vulnerabilities addressed, affected products, and mitigation guidance.
Read more
Microsoft Security Response Center
This blog shares insights on current security threats and Microsoft's responses, detailing specific vulnerabilities and their potential impacts.
Read more
CVE details
The CVE database offers detailed insights on vulnerabilities, including severity, descriptions, and their potential impacts on security.
Read more
Security advisories
Microsoft publishes security advisories for critical vulnerabilities, detailing the issue, its impact, and recommended mitigation steps.
Read more
Secret Link