# CVE-2026-65660: Microsoft SharePoint Server, is it exploitable where you run it

Ledger entry, disclosed 11 Aug 2026, sources read 19 Nov 2026

**The short answer.** CVE-2026-65660 affects Microsoft SharePoint Server and was disclosed 11 Aug 2026 with a CVSS score of 8.8. Exposure needs these conditions: a farm server is below the fixed SharePoint build in the versions table; the attacker has a low-privilege account or reaches an anonymous site. CISA added it to the Known Exploited Vulnerabilities catalog on 25 Sep 2026.

## What the flaw is

CVE-2026-65660 is a code injection flaw (CWE-94) in on-premises SharePoint Server. Microsoft says an authenticated attacker with low-level access to an affected server can send a specially crafted request that runs code on the server. No user interaction is needed. The CVSS 3.1 base score is 8.8 (network, low complexity, low privileges, high impact on confidentiality, integrity and availability).

Microsoft first published the CVE on 11 Aug 2026 as a spoofing flaw with a lower CVSS score. A revision on 27 Aug 2026 changed the title, impact and FAQs to remote code execution. Microsoft calls that revision informational, and the security update was available from 11 Aug 2026. Teams that triaged it as a medium spoofing issue in August should re-rate it.

On its own the bug needs a logged-in account. Previdian reports that the attempts it saw paired it with a second, separate weakness that lets an unauthenticated request reach the same processing on sites that allow anonymous viewing. Previdian, citing Viettel Cyber Security research, says that second weakness was fixed on 9 Jun 2026 and has no CVE identifier in that write-up.

## Are you exposed: each condition and how to check it

| Condition for exposure | How to check it on your system |
| --- | --- |
| a farm server is below the fixed SharePoint build in the versions table | On a SharePoint server, open the SharePoint Management Shell and run (Get-SPFarm).BuildVersion. Or open Central Administration > Upgrade and Migration > Check product and patch installation status. Compare with 16.0.5565.1001 (2016), 16.0.10417.20198 (2019) or 16.0.19725.20522 (Subscription Edition). Check every server, since a partial install leaves the farm exposed. Where Microsoft lists two update packages (2016 and 2019) install both, and confirm in Check product and patch installation status that each server and product shows the new build with no 'upgrade required' state; run PSConfig after the update if the status page says it is needed. |
| the attacker has a low-privilege account or reaches an anonymous site | The anonymous route works only on a farm that lacks the 9 Jun 2026 fix. List who can sign in: Central Administration > Application Management > Manage web applications, then review user policy and site permissions. Any account with a valid sign-in on an exposed site meets the condition. For the anonymous route, in Central Administration > Application Management > Manage web applications > select the web application > Authentication Providers > select the zone, check 'Enable anonymous access', then open Site Settings > Site permissions > Anonymous Access on a site. Previdian says the 9 Jun 2026 fix closes the anonymous route but names no update; the fixed builds in the versions table are later than the June 2026 SharePoint security update builds, so a farm at or above them has that fix too. With anonymous access off, the delivery route needs a signed-in account. Network reach: check which IP addresses and ports the web application binds to in IIS Manager > Sites, and whether the firewall or reverse proxy publishes it to the internet. |

## Affected and fixed versions

| Product line | Affected builds | First fixed build | Update packages |
| --- | --- | --- | --- |
| SharePoint Server 2016 (Enterprise Server 2016 uses the same updates) | Earlier than 16.0.5565.1001 | 16.0.5565.1001 | KB5002905 and KB5002906 |
| SharePoint Server 2019 | Earlier than 16.0.10417.20198 | 16.0.10417.20198 | KB5002894 and KB5002896 |
| SharePoint Server Subscription Edition | Earlier than 16.0.19725.20522 | 16.0.19725.20522 | KB5002893 |

Microsoft says to install every update package offered for the installed product, not just one. The updates may need a restart. Microsoft's FAQ says the same KB applies to SharePoint Server 2016 and SharePoint Enterprise Server 2016.

## If the fix cannot go in yet

- Install the August 2026 SharePoint update for each product on every farm server (KB5002905 and KB5002906, KB5002894 and KB5002896, or KB5002893). Cost: a restart may be needed, and the farm configuration step must finish on every server. This is the only fix, and Microsoft's records list no workaround.
- If you cannot patch yet, turn off anonymous viewing on web applications that do not need it (Previdian). Cost: public visitors must then sign in. This closes only the anonymous route Previdian saw, not the authenticated flaw.
- Limit SharePoint exposure to the internet, for example by placing it behind a VPN or an authenticating reverse proxy. Cost: remote users and partners lose direct access. An attacker with a valid low-privilege account on the internal network can still reach it.

## What to look for

- Previdian hunting guidance: search web logs for POST requests to /_layouts/15/AddGallery.aspx and /_layouts/15/designgallery.aspx, including paths with a repeated /_layouts/ or /_layouts/15/ prefix. The captured requests used the query string job=all&DisplayMode=Edit, sent no Cookie or Authorization header, and came in pairs of bodies of 7,834 and 535,404 bytes.
- Files to look for (Previdian): a web shell at /_layouts/15/sphealth.aspx, and assemblies wt3k3sij.dll (391,680 bytes, SHA-256 d3faa4b443d98f272363f3484a5e6a9bab90979086aa2d31a1694c1dc8178742) and 24e5mo4s.dll (4,096 bytes, SHA-256 a151a8fc193a96aac480fa749547b57c0f33116cf2cb8c82b6aa716c3c47f4b1). Previdian did not see wt3k3sij.dll written to disk on its honeypot.
- Network indicator: source address 169.150.248[.]21 (AS212238, Datacamp Limited), seen on 24 Sep 2026 near 12:00 UTC. The URL http://asdf/_controltemplates/15/AclEditor.ascx appeared in a form field and is not command-and-control infrastructure.
- Hunting only for the older ToolPane.aspx pattern from earlier SharePoint attacks misses this traffic. CISA's KEV entry marks forensic triage as required; its required action cites CISA's BOD 26-04.

## Timeline

| Date | Event | Source |
| --- | --- | --- |
| 9 Jun 2026 | Per Viettel Cyber Security as cited by Previdian, the separate anonymous-delivery weakness is fixed. This is the June 2026 Patch Tuesday; Microsoft's June SharePoint security updates were KB5002873 (Subscription Edition, 16.0.19725.20384), KB5002874 and KB5002876 (2019, 16.0.10417.20153) and KB5002880 and KB5002881 (2016, 16.0.5556.1005). No source ties this weakness to one of those KBs. | [source](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Jun) |
| 11 Aug 2026 | Microsoft publishes the advisory (revision 1.0) as a spoofing issue rated CVSS 3.1 6.5, with the security updates; NVD publishes the record. Microsoft credits khoadha. | [source](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug) |
| 27 Aug 2026 | Microsoft revision 1.1 changes the impact, title and FAQs to remote code execution and the CVSS 3.1 base score to 8.8, marked informational. | [source](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug) |
| 24 Sep 2026 | Previdian captures 12 POST requests from one source on a honeypot near 12:00 UTC and publishes its report. The requests are attempts; Previdian did not recover the final payload or show a compromise. CISA's SSVC entry on the NVD record carries the same date and marks exploitation active. | [source](https://blog.previdian.com/cve-2026-65660-previdian-observes-two-stage-sharepoint-exploitation-attempts/) |
| 25 Sep 2026 | Microsoft revision 1.2 states it had reliable evidence of observed attacks, and CISA adds the CVE to KEV with a due date of 28 Sep 2026. KEV lists ransomware use as Unknown. | [source](https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug) |

Exploited 44 days after disclosure: disclosed 11 Aug 2026, first exploitation reported 24 Sep 2026.

## Exploitation reported so far

Previdian's honeypot received 12 requests from one source address, carrying two payloads per path: one to disable a .NET deserialization safeguard, then a larger one carrying an assembly loader. Previdian classed the traffic as an attempted pre-authentication chain.

## Why runtime reachability settles it

A build check says whether the farm is patched, but exposure also depends on who can reach the server and whether any site allows anonymous viewing, which are facts about the running farm. The first row of the checks table settles the patch state and the second row settles who can reach the flaw. KEV and Microsoft confirm attacks, so a reachable unpatched farm is urgent. See [runtime reachability](/methods/runtime-reachability/) for what the method proves and misses.

## Related pages

- [CVE-2026-68820: Microsoft Windows AFD for WinSock](/ledger/cve-2026-68820/)
- [CVE-2026-42018: JFrog Artifactory](/ledger/cve-2026-42018/)
- [CVE-2026-41709: Broadcom VMware ESX, VMware ESX insufficient logging](/ledger/cve-2026-41709/)

## Sources

- CVE-2026-65660: NVD record: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-65660 (read 19 Nov 2026)
- CVE-2026-65660: CISA KEV entry (feed version 2026.11.18): https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-65660 (read 19 Nov 2026)
- CVE-2026-65660: Microsoft advisory (MSRC API record: description, FAQs, severity): https://api.msrc.microsoft.com/sug/v2.0/en-US/vulnerability/CVE-2026-65660 (read 19 Nov 2026)
- CVE-2026-65660: Microsoft advisory (MSRC August 2026 CVRF: fixed builds, KBs, revision history): https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug (read 19 Nov 2026)
- CVE-2026-65660: Previdian research on exploitation attempts: https://blog.previdian.com/cve-2026-65660-previdian-observes-two-stage-sharepoint-exploitation-attempts/ (read 19 Nov 2026)
- CVE-2026-65660: Microsoft advisory (MSRC June 2026 CVRF: SharePoint KBs and builds of 9 Jun 2026): https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Jun (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/ledger/cve-2026-65660/
