• Home
  • About
  • Locations
  • Contact Us
logologologologo
  • Plan
    • AI Governance & Risk Management
    • Acquisition & VC
    • vCISO
    • Policies & Procedures
    • Strategy & Security Program Creation
    • Risk Management
  • Attack
    • Penetration Testing
    • AI Penetration Testing
    • Mobile Application Penetration Testing
    • Red Teaming
    • Web Application Penetration Testing
    • PTaaS
    • IOT Penetration Testing
  • Defend
    • Office 365 Security
    • HIPAA Compliance
    • PCI Compliance
    • Code Reviews
    • Blockchain Security Analysis
    • Vulnerability Assessments
  • Recover
    • Ransomware Recovery
    • Expert Witness
    • Forensics
  • Learn
    • Resources
    • Penetration Testing Training
    • Blog
  • Tools
    • Wp2shell Checker
    • php2shell checker
  • Instant Quote
✕

Critical Microsoft Patch Tuesday Fixes Teams Need Now

July 15, 2026
Written By: author avatar James Knight
author avatar James Knight
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm’s elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio

The July 2026 Microsoft Patch Tuesday fixed a record 622 CVEs, and attackers already exploited two of them: CVE-2026-56164 in SharePoint Server and CVE-2026-56155 in AD FS. Therefore, teams should patch those zero-days first, then finish Kerberos RC4 preparation, and finally close the SharePoint JWT chain that attackers abused in August.

What Did the July 2026 Microsoft Patch Tuesday Fix?

Microsoft shipped the release on July 14, 2026. By the most common count, it covered 622 CVEs, almost triple June’s total of 206, with Windows accounting for 416 fixes and Office for 164. However, tallies range from about 570 to 622, because some trackers count the Chromium fixes inside Microsoft Edge and others do not. Either way, the release set a record, and nearly 60 of its flaws carried a Critical rating.

Microsoft had warned on July 9 that customers should expect more fixes in each release as AI helps defenders find bugs earlier. For example, in May 2026 Microsoft said its MDASH system, a multi-model agentic scanning harness, found 16 new flaws across Windows networking and authentication. In other words, large releases like this one will likely become normal.

Which Zero-Days Should Teams Patch First?

This Microsoft Patch Tuesday fixed three zero-days, but only two came under attack. Accordingly, CISA added both exploited flaws to its catalog the same day, as its July 14 KEV alert shows, and gave federal agencies until July 17 to act.

CVEProductTypeStatus
CVE-2026-56164SharePoint ServerElevation of privilege, no login neededExploited; CISA KEV July 14
CVE-2026-56155Active Directory Federation ServicesElevation of privilege, CVSS 7.8Exploited; CISA KEV July 14
CVE-2026-50661Windows BitLockerSecurity feature bypass, physical accessPublicly disclosed; not exploited at release

Why Does the SharePoint Zero-Day Lead the List?

CVE-2026-56164 stems from missing authentication for a critical function (CWE-306), so an unauthenticated attacker can raise privileges over the network. Strikingly, Microsoft scores it only 5.3 Medium under CVSS v3.1, while NVD scores the same flaw 9.8 Critical. Because attackers exploited it anyway, a CVSS sort of this Microsoft Patch Tuesday would have buried a live zero-day.

The fix covers three supported SharePoint versions. In addition, CISA’s SharePoint hardening alert urges teams to turn on AMSI with full request body scanning, hunt for machine key harvesters before they rotate IIS machine keys, and block outside access to Central Administration.

SharePoint versionFixed build
Subscription Edition16.0.19725.20434 (KB5002882)
SharePoint Server 201916.0.10417.20175 (KB5002883)
SharePoint Enterprise Server 201616.0.5561.1001 (KB5002891)

Notably, SharePoint Server 2019 reached the end of support on July 14, 2026, the same day as this release. SQL Server 2016 also reached the end of support that day. Consequently, any farm still running those products should plan a migration now.

Why Does the AD FS Flaw Threaten Identity?

AD FS stores the keys that protect its token signing certificates in the Distributed Key Manager container in Active Directory. According to Microsoft’s CVE-2026-56155 entry, an attacker who can read that key material through overly broad permissions can decrypt the token signing keys. Then the attacker can forge tokens that every connected service trusts.

The July update added detection of unsafe container permissions and an opt-in repair. Since the October 13, 2026 update, AD FS repairs those permissions by default, leaving access only for Domain Admins, Enterprise Admins, SYSTEM and the AD FS service account. Still, farms built on Windows Server 2012 or 2012 R2 may log Event 1137, which means the service account needs extra rights before the repair can finish.

What Happened to the SharePoint JWT Chain?

The July release also fixed CVE-2026-55040, a JWT authentication bypass in SharePoint with a CVSS score of 9.1. Researchers showed that an attacker who knows a user’s identifier can act as that user, and then chain the bypass with a separate RCE flaw. At first, the RCE half remained unpatched, so the July fix broke the chain at the login step.

Since then, the threat has grown. On August 11, 2026, researchers published full details and a working script, and honeypots logged attempts the next day. As a result, CISA added CVE-2026-55040 to KEV on August 18, while Microsoft patched the paired RCE flaw, CVE-2026-63520, in its August release. Therefore, a SharePoint farm needs both the July and August updates.

How Can Kerberos RC4 Hardening Break Services?

Microsoft has phased out RC4 for Kerberos service tickets in three steps, according to support article KB5073381. First, the January 13, 2026 update added audit events 201 through 209 to the System log. Next, the April 14 update switched the default to AES for accounts with no explicit encryption setting. Finally, updates from July 2026 onward removed the rollback registry value, so the change now sticks.

Because of that, legacy service accounts and non-Windows devices that only speak RC4 can suddenly fail to authenticate. The outage can look like an attack at first, although the real cause is old Kerberos settings. For that reason, identity and application owners should clear every warning event before they push updates to domain controllers.

Six priorities from the July 2026 Microsoft Patch Tuesday release
Six priorities from the July release.

How Did the Timeline Unfold?

Several dates tied to this Microsoft Patch Tuesday sit outside July itself. Accordingly, use this table to check that your patch history covers each step.

Date (2026)Event
January 13Kerberos RC4 audit phase begins
April 14Kerberos defaults to AES for accounts without an explicit setting
MayMicrosoft details MDASH and 16 AI-found Windows flaws
July 9Microsoft warns of larger security releases
July 14Record release ships; CISA adds CVE-2026-56164 and CVE-2026-56155 to KEV; SharePoint Server 2019 and SQL Server 2016 reach end of support
July 17CISA deadline for federal agencies
August 11Public exploit for CVE-2026-55040 appears
August 18CISA adds CVE-2026-55040 to KEV; August release patches CVE-2026-63520
October 13AD FS repairs unsafe DKM permissions by default

How Strong Is the Evidence?

Microsoft and CISA confirm the core Microsoft Patch Tuesday facts, yet a few figures depend on who counts. Therefore, this table separates confirmed points from reported and open ones.

ClaimStatus
Exploitation of CVE-2026-56164 and CVE-2026-56155Confirmed by Microsoft and CISA KEV
Record size of the releaseConfirmed; totals range from about 570 to 622 depending on Chromium fixes
SharePoint zero-day severity5.3 from Microsoft, 9.8 from NVD
Exploitation of CVE-2026-55040Confirmed by CISA KEV on August 18
BitLocker bypassPublicly disclosed; Microsoft saw no exploitation at release
Who exploited the two zero-daysNot published
Scores for VMSwitch and other critical bugsReported by one research group

What Are the Critical Microsoft Patch Tuesday Fixes?

Order matters for every Microsoft Patch Tuesday fix this month, because one wrong step can cause an outage or leave a door open. Work through these seven fixes in sequence.

Fix 1: Patch SharePoint Through the August Release

First, bring every SharePoint farm to at least the July builds above, then apply the August update for CVE-2026-63520. After that, turn on AMSI full mode, remove any machine key harvesters, rotate machine keys, and keep Central Administration off the internet.

Fix 2: Patch AD FS and Confirm the DKM Repair

Next, install the October 13, 2026 update or later on every AD FS server. Then check the AD FS Admin log for Events 1133 or 1135, which show a secure container, and fix any Event 1136 or 1137 before you move on.

Fix 3: Clear Kerberos RC4 Warnings

Meanwhile, review Events 201 through 209 on every domain controller. Reset passwords on old service accounts so they gain AES keys, and set an explicit encryption type only for the few services that truly need RC4.

Fix 4: Retire Unsupported SharePoint and SQL Server

Then, move SharePoint Server 2019 and SQL Server 2016 workloads to supported versions. Until you finish, isolate those servers from the internet, because they no longer receive security updates.

Fix 5: Patch Network Facing Critical Bugs

After that, prioritize reported critical flaws in network services, including Windows VMSwitch CVE-2026-57092, Remote Desktop CVE-2026-56190, DHCP Server CVE-2026-50518 and SharePoint CVE-2026-50522. Likewise, review the Exchange Server cross site scripting flaw CVE-2026-55008.

Fix 6: Patch BitLocker on Mobile Devices

Also, roll out the fix for CVE-2026-50661 in your normal cycle, starting with laptops for executives and travelers. In addition, consider a pre-boot PIN, since this bug requires physical access.

Fix 7: Triage by Risk Instead of CVSS

Finally, build each patch queue around exploitation status, internet exposure, identity impact, EPSS and business criticality. That method would have put a 5.3 SharePoint zero-day at the top on day one.

How to triage Microsoft Patch Tuesday fixes by risk instead of CVSS
How to triage by risk instead of CVSS.

Which Commands Confirm Your Coverage?

Run these PowerShell checks to confirm the SharePoint build, the AD FS repair and any remaining Kerberos RC4 warnings. Specifically, run the first in the SharePoint Management Shell, the second on an AD FS server, and the third on each domain controller.

(Get-SPFarm).BuildVersion Get-WinEvent -LogName “AD FS/Admin” | Where-Object { $_.Id -in 1132,1133,1135,1136,1137 } | Select-Object TimeCreated,Id,Message -First 20 Get-WinEvent -FilterHashtable @{LogName=”System”; Id=201,202,203,204,205,206,207,208,209} | Select-Object TimeCreated,Id,Message -First 50

Why Does CVSS Alone Fail at This Scale?

Ultimately, a Microsoft Patch Tuesday with more than 600 fixes overwhelms any team that sorts by score alone. The SharePoint zero-day shows the problem clearly, because its vendor score said Medium while attackers already used it. Our 2026 Mid Year Threat Pattern Report tracks the same gap between scores and real attacks, and our analysis of an AI PowerShell Active Directory attack shows why identity systems such as AD FS deserve top priority.

For that reason, threat informed patching needs accurate asset data. Our team runs vulnerability assessments that map exposed SharePoint and AD FS servers, penetration testing that proves whether a missed patch is reachable, and a PTaaS platform that keeps that testing continuous.

Key Takeaways

  • The July 2026 Microsoft Patch Tuesday fixed a record 622 CVEs, including three zero-days
  • CVE-2026-56164 in SharePoint and CVE-2026-56155 in AD FS came under attack, and CISA added both to KEV on July 14
  • Microsoft scored the SharePoint zero-day only 5.3, which shows why CVSS alone misleads
  • Attackers exploited the SharePoint JWT bypass CVE-2026-55040 in August, so farms need the August update as well
  • Clear Kerberos RC4 warnings before patching domain controllers, because the July update removed the rollback option

Frequently Asked Questions About Microsoft Patch Tuesday

What Did the July 2026 Microsoft Patch Tuesday Fix?

Microsoft fixed a record 622 CVEs by the most common count, including three zero-days. Two of them, CVE-2026-56164 in SharePoint Server and CVE-2026-56155 in AD FS, were already under attack, and CISA added both to its KEV catalog on July 14, 2026.

Why Do CVE Counts Differ Between 570 and 622?

Some trackers include the Chromium fixes that ship with Microsoft Edge, while others leave them out. As a result, totals for the same release range from about 570 to 622.

Why Does Microsoft Score the SharePoint Zero-Day as Medium?

Microsoft rates CVE-2026-56164 at 5.3 under CVSS v3.1, while NVD scores it 9.8. However, attackers exploit it without credentials over the network, so its real risk sits far above its vendor score.

What Changed for AD FS After July?

The July update added detection of unsafe permissions on the AD FS Distributed Key Manager container and an opt-in fix. From the October 13, 2026 update onward, AD FS repairs those permissions by default unless an administrator opts out.

Did Attackers Exploit the SharePoint JWT Bypass?

Yes. A public proof of concept for CVE-2026-55040 appeared on August 11, 2026, attempts began the next day, and CISA added it to KEV on August 18. Microsoft patched the paired RCE flaw, CVE-2026-63520, in August.

How Can Kerberos RC4 Hardening Break Services?

Since April 2026, domain controllers default to AES for accounts without an explicit encryption setting. The July update also removed the rollback option, so services that still depend on RC4 can fail to authenticate.

Should Teams Use CVSS Alone to Prioritize?

No. This release proves why, because Microsoft scored an exploited zero-day at 5.3. Instead, rank each Microsoft Patch Tuesday fix by exploitation status, exposure, identity impact, EPSS and business criticality.

author avatar
James Knight Senior Principal, and lead threat intelligence analyst
James Knight is a well-known cybersecurity expert, international keynote speaker, and Senior Principal at Digital Warfare, a global cybersecurity consulting firm headquartered in McLean, Virginia, USA. Digital Warfare provides penetration testing, red teaming, vCISO, and many other services to enterprise organizations and government entities globally and across the United States. With over 25 years of hands-on experience at the intersection of offensive security and real-world threat intelligence, James has conducted pen tests, security assessments, vulnerability research, and adversarial analysis for corporate enterprises and government clients spanning financial services, critical infrastructure, and defense-adjacent sectors. His work covers the full spectrum of modern enterprise threats including advanced persistent threat campaigns, ransomware group tradecraft, supply chain compromise, AI-augmented attack techniques, and zero-day vulnerability exploitation. James is a recognized and frequently cited voice on cybersecurity in both specialist and mainstream media. Many well-known news sites, including The Daily Mail, have quoted him on many occasions: on ransomware payment policy in the context of the Colonial Pipeline attack, on how agentic AI is expected to reshape cyber warfare over the next 25 years, and on the security implications of the latest OpenAI security incident. His analysis has also been cited on Medium, where independent cybersecurity researchers have quoted his insights on supply chain security and AI-driven attack techniques. On supply chain risk, James has described the threat in terms that practitioners recognize immediately: supply chain attacks exploit the trust organizations place in third parties, requiring defenders to map every dependency like a battlefield and probe for weaknesses that could cascade across entire networks. On AI-driven attacks, his assessment reflects the same operational directness: AI-powered attacks exploit the enterprise fascination with new technology, requiring penetration testers to treat every unverified component as a potential payload delivery mechanism. His firm has been featured as a cybersecurity resource in FinancialContent and referenced across multiple professional data platforms including ZoomInfo and Datanyze as a specialist cybersecurity consulting firm serving Fortune 500 and SME organizations. At Digital Warfare, James leads the team and authors the Digital Warfare Threat Intelligence blog, publishing daily analysis of confirmed cybersecurity incidents sourced exclusively from verified primary sources including CISA advisories, vendor security bulletins, and leading threat intelligence publications. His analysis is built for security practitioners and business leaders who need actionable intelligence rather than vendor marketing. His original research includes the Digital Warfare 2026 Mid-Year Threat Pattern Report, an analysis of 28 confirmed threat incidents tracked between January and August 2026 that introduced three named security frameworks now used by enterprise security teams. The Zero-Day Priority Framework establishes a tiered patching classification system grounded in confirmed 2026 exploitation data showing that 73 percent of zero-days are weaponized within 72 hours of public disclosure. The Supply Chain Attack Taxonomy defines three distinct classes of supply chain compromise, each requiring different defensive controls and monitoring approaches. The AI Augmentation Classification documents three confirmed maturity levels of AI-assisted attack capability observed in real-world 2026 incidents, from AI-generated custom malware at Level One through fully autonomous ransomware operations at Level Three. Digital Warfare was founded in 2012 and serves corporations and governmental entities seeking rigorous security assessment and strategic security leadership from practitioners with genuine operational experience. Every member of the firm's elite team brings over 25 years of cybersecurity experience to every client engagement. Connect with James on LinkedIn or follow his threat intelligence updates at digitalwarfare.com/blog.
See Full Bio
Penetration Testing Ransomware Incident Response Threat Intelligence Zero-Day Vulnerability Research
social network icon social network icon
Share
Copyright © Digital Warfare. All rights reserved.
  • Home
  • About
  • Locations
  • Contact Us