Between March and September 2026, CISA added eight Microsoft SharePoint Server vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. SharePoint was one of the most recurrent names in the year's list, which we analyse in full in our review of the exploited vulnerabilities of 2026. Looking back from November, the pattern is hard to miss: five of the eight allow code execution, three are authentication or spoofing flaws, one is known to be used in ransomware campaigns, and on 14 July 2026, the day Microsoft shipped four of these fixes, SharePoint Server 2016 and 2019 reached the end of extended support. If you still run SharePoint on your own servers, this article covers what happened, how to check whether your farm is reachable from the internet, what to do beyond installing the update, and how to choose between Subscription Edition and SharePoint Online.
- CISA added eight SharePoint Server CVEs to the KEV catalog between 18 March and 25 September 2026. Five of them allow remote code execution.
- Microsoft's advisories flagged three as already exploited when the fix was released. The others entered KEV between about a week and more than two months after the patch.
- CISA marks CVE-2026-45659 as known to be used in ransomware campaigns.
- SharePoint Server 2016 and 2019 left extended support on 14 July 2026. Subscription Edition and SharePoint Online are the supported paths.
- Installing the update is not the end of the job. Microsoft's 2025 guidance for SharePoint (AMSI, machine key rotation, hunting for web shells) remains the reference playbook.
The list: eight SharePoint entries in KEV, March to September 2026
The table below combines two primary sources: the CISA KEV catalog, which records the date a vulnerability was added because there is evidence of exploitation, and the Microsoft Security Response Center (MSRC) advisories, which give the type of flaw, the CVSS score and the date the fix was released. All eight affect SharePoint Enterprise Server 2016, SharePoint Server 2019 and SharePoint Server Subscription Edition, according to the products Microsoft lists for each CVE.
| CVE | Type (Microsoft) | CVSS | Who can exploit it | Fix released | Added to KEV |
|---|---|---|---|---|---|
| CVE-2026-20963 | Remote code execution (deserialization of untrusted data) | 9.8 | No credentials needed | 13 Jan 2026 | 18 Mar 2026 |
| CVE-2026-32201 | Spoofing (improper input validation) | 6.5 | No credentials needed | 14 Apr 2026 | 14 Apr 2026 |
| CVE-2026-45659 | Remote code execution (deserialization) | 8.8 | Needs a valid account | 21 May 2026 | 1 Jul 2026, ransomware use known |
| CVE-2026-56164 | Elevation of privilege (missing authentication for a critical function) | 5.3 | No credentials needed | 14 Jul 2026 | 14 Jul 2026 |
| CVE-2026-58644 | Remote code execution (deserialization) | 9.8 | No credentials needed | 14 Jul 2026 | 16 Jul 2026 |
| CVE-2026-50522 | Remote code execution (deserialization) | 9.8 | No credentials needed | 14 Jul 2026 | 22 Jul 2026 |
| CVE-2026-55040 | Security feature bypass (weak authentication) | 9.1 | No credentials needed | 14 Jul 2026 | 18 Aug 2026 |
| CVE-2026-65660 | Remote code execution (code injection) | 8.8 | Needs a valid account | 11 Aug 2026 | 25 Sep 2026 |
Three details stand out. First, Microsoft's advisories for CVE-2026-32201, CVE-2026-56164 and CVE-2026-58644 already reported exploitation when the update was published: these were zero-days, and anyone without the July update was exposed from day one. Second, the other five reached KEV between about a week (CVE-2026-50522) and more than two months (CVE-2026-20963, patched in January and added in March) after the fix. A KEV date marks when CISA had evidence of exploitation, not when exploitation began, but the lesson holds: a server that skips a monthly update stays exposed long after the fix exists. Third, CVE-2026-45659 carries the "Known" flag for ransomware campaign use, the clearest signal in the catalog that a flaw has moved from opportunistic scanning to extortion operations.
Two more items complete the picture. On 14 July CISA also added CVE-2026-56155 in Active Directory Federation Services, a local elevation of privilege for an attacker who already has access: the servers that handle federated sign-in around SharePoint are targets too. And in August CSIRT Italia issued an alert on a further SharePoint flaw, CVE-2026-63520, affecting 2016, 2019 and Subscription Edition, as listed in ACN's Operational Summary for August 2026.
From July onwards, the KEV entries for SharePoint also changed in tone. Their required action now refers to CISA's Binding Operational Directive 26-04, "Prioritizing Security Updates Based on Risk", together with forensics triage requirements. The directive binds only US federal agencies, but the signal for a European company is useful: once a flaw is known to be exploited, the question is no longer only "have we patched?" but also "were we compromised before we patched?". We explain how KEV, EPSS and SSVC fit together in our guide to vulnerability prioritisation.
Why SharePoint keeps coming back
Deserialization: the same class of bug, again and again
Four of the eight CVEs are described by Microsoft as deserialization of untrusted data, and a fifth as code injection. SharePoint is a large ASP.NET application that accepts complex objects from the client and rebuilds them on the server. When that reconstruction trusts data it should not, an attacker can make the server run code of their choosing inside the IIS worker process. The fact that the same class of flaw returned in January, May and twice in July says less about any single bug than about the size and age of the code base: on a product this large, you should expect more of the same and plan your patching accordingly.
Authentication and spoofing flaws
The other three entries are about who the server thinks you are. CVE-2026-32201 is a spoofing flaw caused by improper input validation, CVE-2026-56164 is a missing authentication check on a critical function that lets an attacker elevate privileges, and CVE-2026-55040 is weak authentication that bypasses a security feature. None needs a valid account. On their own, some score modestly (5.3 and 6.5), but in practice authentication flaws are what turn an "authenticated only" remote code execution, like CVE-2026-45659 or CVE-2026-65660, into something an outsider can reach. Score each CVE on its own and you can underestimate the combination.
A web application that sits on your identity
SharePoint is not a brochure website. It is joined to Active Directory, runs under service accounts that often have broad rights, and holds documents that matter: contracts, procedures, project files. A compromised SharePoint server gives an attacker a foothold with credentials and data in the same place, and often a path towards the domain. This is why the AD FS entry of 14 July matters in the same story, and why a SharePoint incident should be handled as an identity incident, not only as a web server fix.
Is your SharePoint reachable from the internet?
Most of the CVEs above can be exploited "over a network". Whether that network includes the whole internet depends on choices made years ago, and many IT teams do not have a complete answer. The usual ways a SharePoint farm ends up exposed are:
- An extranet for partners or customers, published directly or through a reverse proxy that forwards traffic without requiring authentication first.
- Remote access for staff set up during an emergency and never reviewed, with the site on a public hostname instead of behind the VPN.
- Test, staging or migration farms with a public IP address, left running after a project ended and missing the monthly updates.
- Federation infrastructure such as AD FS and its proxies, which must face the internet to work and therefore needs the same attention.
The only reliable way to answer the question is to look from the outside, the way an attacker does: list every hostname and IP address tied to your domains, check which ones answer, and identify which of them run SharePoint or IIS with a SharePoint login page. A CMDB tells you what you think you have; an external scan tells you what is actually reachable. If you find a SharePoint server that should not be public, the fastest mitigation is to remove it from the internet or put it behind the VPN or an authenticating gateway while you patch.
Patch, rotate, hunt: what to do beyond the update
1. Install the current security update on every server in the farm
SharePoint updates must be installed on every server in the farm, followed by the configuration wizard, otherwise part of the farm keeps running vulnerable code. Check the build number on each server against the one in the Microsoft advisory, rather than trusting the patch management console. For the August fix of CVE-2026-65660, for example, MSRC lists KB5002893 for Subscription Edition, KB5002894 and KB5002896 for 2019, and KB5002905 and KB5002906 for 2016.
2. Use the 2025 playbook: AMSI, machine keys, IIS restart
The most complete reference Microsoft has published for an exploited SharePoint flaw is its July 2025 guidance for CVE-2025-53770, the "ToolShell" campaign. It concerns an earlier vulnerability, but its steps are the right baseline for any SharePoint deserialization flaw:
- Enable the Antimalware Scan Interface (AMSI) integration in SharePoint, in Full Mode where request body scanning is available, together with Microsoft Defender Antivirus on every SharePoint server.
- If AMSI cannot be enabled, disconnect the server from the internet until the update is installed, or limit unauthenticated traffic with a VPN, an authenticating proxy or an authentication gateway.
- After updating, rotate the ASP.NET machine keys with the PowerShell cmdlets
Set-SPMachineKeyandUpdate-SPMachineKey, then restart IIS on every server withiisreset.exe. A key read by an attacker before the patch remains valid after it. - Deploy an EDR such as Defender for Endpoint, or an equivalent, to detect post-exploitation activity.
3. Hunt for web shells and persistence
In 2025 Microsoft's indicator of successful exploitation was a file named spinstall0.aspx in the LAYOUTS folders. You should not assume the 2026 campaigns used the same file name, but the method carries over: look for .aspx files created or modified in the SharePoint folders since the vulnerability was published, for the IIS worker process (w3wp.exe) launching cmd.exe or PowerShell, for changes to web.config and machine keys you did not make, and for new accounts or group memberships in Active Directory. If you find anything, treat it as an incident: isolate, preserve evidence, and only then clean up. This is exactly the "forensics triage" that CISA now pairs with patching.
2016 and 2019 are out of support: the decision you cannot postpone
According to Microsoft's lifecycle pages for SharePoint Server 2019 and SharePoint Server 2016, extended support for both ended on 14 July 2026, the same Patch Tuesday that brought fixes for CVE-2026-56164, CVE-2026-58644, CVE-2026-50522 and CVE-2026-55040. Microsoft's advisory for CVE-2026-65660, published on 11 August, still lists updates for 2016 and 2019; do not plan around further fixes. A product without support is a product whose next deserialization flaw may have no update at all.
There are three realistic paths:
| Option | What changes | What stays your responsibility |
|---|---|---|
| SharePoint Server Subscription Edition | Supported under the Modern Lifecycle Policy, so it keeps receiving security updates as long as you stay current | The servers, the monthly updates, AMSI, machine keys, exposure to the internet and monitoring |
| SharePoint Online (Microsoft 365) | Microsoft runs and patches the servers. The 2026 CVEs above list only on-premises products, and Microsoft stated that SharePoint Online was not affected by the 2025 flaws | Configuration: external sharing, guest access, conditional access, MFA, OAuth apps and audit logging |
| Staying on 2016 or 2019 for now | Nothing improves over time | Everything, plus the risk of a flaw without a fix. Only acceptable short term, with the farm off the internet, reachable only via VPN, closely monitored and with a dated migration plan |
The choice depends on customisations, integrations, data residency requirements and how much server operations you want to keep. From a security standpoint, the point is simpler: an internet-facing SharePoint 2016 or 2019 in November 2026 is a risk you can no longer manage with patches alone. Moving to SharePoint Online also does not remove the work, it moves it: misconfigured sharing in Microsoft 365 is an exposure of its own.
Monitoring: what to watch on a SharePoint server
Even with every update installed, the gap between the publication of a zero-day and your next maintenance window is where an attacker operates. Three of this year's eight were exploited before a fix existed. The signals worth collecting and watching around the clock are:
- Process lineage on SharePoint servers: w3wp.exe starting command shells, PowerShell or unusual binaries.
- File changes in the SharePoint and IIS folders, especially new .aspx files.
- Changes to web.config, machine keys and farm configuration outside change windows.
- Authentication anomalies on SharePoint, AD FS and the domain controllers, including service accounts signing in from unusual hosts.
- Outbound connections from SharePoint servers to the internet, which a document server rarely needs to make.
Collecting these logs is the easy part. Someone has to read them at 3 a.m. on a Sunday in August, decide whether a w3wp.exe child process is an admin script or a web shell, and act. For a mid-sized company without an in-house SOC, that is the hardest piece to cover.
Checklist for SharePoint on-premises
- Inventory every SharePoint and AD FS server, including test and migration farms, with version and build.
- Check from the outside which of them are reachable from the internet, and remove or put behind VPN or pre-authentication any that do not need to be public.
- Install the latest security update on every server in each farm and verify the build against the Microsoft advisory.
- Enable AMSI in Full Mode and antivirus on every SharePoint server.
- Rotate the ASP.NET machine keys after updating and restart IIS.
- Hunt for web shells, unexpected .aspx files, suspicious child processes of w3wp.exe and changes in Active Directory since the first relevant CVE.
- If you run 2016 or 2019, take the decision now: Subscription Edition or SharePoint Online, with a date.
- Send SharePoint, IIS, AD FS and domain controller logs to a monitoring service that someone watches 24/7.
- Subscribe to the CISA KEV feed and to CSIRT Italia alerts, and treat every new SharePoint entry as an emergency change.
How Orizon can help
RECON External answers the first question in this article: what you actually expose. Starting from your domain names, it finds subdomains, open ports and web services, fingerprints the technologies, matches what it detects against known CVEs weighted by CISA KEV, EPSS, Exploit-DB and Metasploit, then tests each finding from an isolated server and marks it Proven, To verify or Closed, with the evidence of every test. The proofs only read; they never change your systems. If a forgotten SharePoint extranet is answering on the internet, you will see it and know whether the issue is real. For the second question, who watches your servers when the next zero-day appears, Oversight provides 24/7 monitoring on the CYREBRO platform, with Orizon installing the service on your stack and stepping in with incident response and forensic investigation when needed. For the full picture of the year's exploited vulnerabilities, read our 2026 KEV analysis.