// Güvenlik

The code execution vulnerability in SharePoint is being used in ransomware attacks

CVE-2026-65660, which allows remote code execution in Microsoft SharePoint, has been added to CISA's catalog of actively exploited vulnerabilities. The remediation deadline is September 28, 2026.

A security vulnerability in Microsoft SharePoint that allows code execution over the network has been added to the U.S. Cybersecurity and Infrastructure Security Agency’s (CISA) Known Exploited Vulnerabilities (KEV) catalog. The catalog gives a remediation date of September 28, 2026 for the vulnerability, tracked as CVE-2026-65660. In the entry, the vulnerability is flagged as being associated with ransomware campaigns.

What the vulnerability does

According to the entry in the National Vulnerability Database (NVD), the issue stems from insufficient control over code generation in SharePoint — that is, a type of code injection. An attacker exploiting the vulnerability can execute code over the network. According to Microsoft’s assessment, logging in with a low-privileged account is enough for this, and the victim doesn’t need to take any action during the attack. The CVSS 3.1 score is 8.8 (high).

The classification changed later

When the vulnerability was first recorded, it was described as “spoofing.” By August 27, Microsoft had updated the entry to remote code execution. This discrepancy created confusion about how serious the vulnerability was and made news in the security press. In today’s records, the vulnerability appears as authenticated remote code execution.

Exploitation attempts from the field

The security firm Previdian published on September 24 the attempts that came into its own SharePoint honeypot. A total of 12 POST requests were sent from a single source IP to six different addresses. The targeted pages include /_layouts/15/AddGallery.aspx and /_layouts/15/designgallery.aspx, and the requests used the DisplayMode=Edit parameter and the MSOTlPn_Uri and MSOTlPn_DWP fields. The attack is two-stage: the first payload tries to disable a deserialization protection on the .NET side, while the second payload aims to run an encrypted assembly loader. The firm adds that it saw no cookie or authorization header in the requests, but that the observation was made in a honeypot and it isn’t proven that every attempt would work in a real installation.

What you should do

Organizations running a SharePoint server need to apply the patch published in Microsoft’s update guidance. The patch alone isn’t enough: security experts recommend reviewing anonymous access settings and searching server logs for unusual POST requests to pages under /_layouts/15/. Since the vulnerability allows code execution, if the patch is delayed, the possibility that an attacker leaves themselves persistent access on the server should also be taken into account.

This isn’t a vulnerability that directly concerns home users; however, on-premises SharePoint installations are still at the center of document and process management in many organizations. If such a server is accessible from the internet, the update shouldn’t be put off until the next maintenance window.

Source: CISA KEV · NVD

// JOIN THE CONVERSATION

Share your experience

Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.

// KEEP READING

One more note.

All posts ↗︎