DE EN IT

~/exploited / cve-2026-65660

CVE-2026-65660: Microsoft SharePoint

According to CISA this vulnerability is already used in attacks (added on 25 September 2026).

Key facts

CVECVE-2026-65660
VendorMicrosoft — SharePoint
VulnerabilityMicrosoft SharePoint Code Injection Vulnerability
Added25 September 2026
Deadline (US agencies)28 September 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.8 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: low needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 9.85%. Higher than 95.7% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-94 — Code Injection
Affected versionssharepoint server: < 16.0.19725.20522
sharepoint server 2016
sharepoint server 2019

Description (NVD)

Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.

Patches and vendor advisories

Description (CISA)

Microsoft SharePoint contains a code injection vulnerability which could allow an authorized attacker to execute code over a network.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether Microsoft SharePoint is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 25 September 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).