Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-45659: Authenticated Remote Code Execution in Microsoft SharePoint Server

Published May 22, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 3 in a dayToday
CVSS8.8High · v3.1
EPSS80.2%100th percentile
CISA KEVYesAdded Jul 1, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2026-45659CWE-502 · Deserialization of Untrusted Data

CVE-2026-45659 is an insecure deserialization vulnerability in on-premises Microsoft SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition. An authenticated, low-privileged attacker with Site Member permissions can submit a crafted serialized payload that SharePoint processes through a vulnerable .NET serializer, causing arbitrary code execution in the IIS worker process. Exploitation occurs over the network with low attack complexity and requires no user interaction. The vulnerability has a CVSS v3.1 base score of 8.8 and is actively exploited, including in ransomware attacks. SharePoint Online and Microsoft 365 are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality, integrity, and availability of the affected SharePoint server through arbitrary code execution under the IIS worker process identity. Potential consequences include sensitive-document disclosure, SharePoint content modification, malware or web-shell deployment, and service disruption. Access to credentials and internal resources may support lateral movement, depending on the process account's permissions. Attacks chaining this vulnerability with other SharePoint flaws have included IIS machine-key theft, persistence, and malware deployment. Stolen machine keys can enable continued exploitation after patching unless compromise artifacts are removed and the keys are rotated.

Mitigation

If you can’t patch tonight, do this now.

Avoid direct internet exposure of SharePoint servers; where external access is necessary, use an authenticated reverse proxy and restrict access to trusted networks. Block external access to Central Administration and enforce least privilege for SharePoint accounts. Enable supported SharePoint AMSI integration and IIS worker-process scanning, with Full request-body scanning where available. Review SharePoint, IIS, Windows, EDR, and proxy telemetry for anomalous requests, unexpected worker-process child processes, web shells, unauthorized IIS modules, and machine-key access. Verify backups and restoration procedures. These controls supplement rather than replace security updates.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates to every affected server in the SharePoint farm. Minimum fixed builds for this vulnerability are 16.0.5552.1002 for SharePoint Server 2016 and SharePoint Enterprise Server 2016, 16.0.10417.20128 for SharePoint Server 2019, and 16.0.19725.20280 for SharePoint Server Subscription Edition. Prefer current security updates that also address related SharePoint vulnerabilities, and verify successful installation on every farm server. For suspected or confirmed compromises, isolate affected systems, preserve forensic evidence, investigate and remove web shells, malicious IIS modules, and key-harvesting artifacts before rotating IIS/ASP.NET machine keys and exposed credentials. Patching alone does not remove established persistence.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-45659-SharePoint-RCEThis repository is a small standalone Python exploit project consisting of one main script (`CVE-2026-45659.py`), a README, and a minimal `.gitignore`. It is not part of a known exploitation framework. The script is presented as an authenticated RCE exploit for a claimed SharePoint deserialization issue, CVE-2026-45659, affecting SharePoint Server 2019, 2022, and Subscription Edition before May 2026. The exploit’s structure is straightforward: it defines a banner, a payload generator, a `SharePointClient` class for HTTP interaction, and a `main()` CLI entry point. The payload generator creates a base64-encoded JSON structure that simulates a malicious .NET deserialization chain using `System.Diagnostics.Process` / `ProcessStartInfo` to run an operator-supplied command. This is notable because the code comments explicitly state the payload is a simplified simulation rather than a full LosFormatter/ObjectStateFormatter gadget chain, suggesting the repository is more of an operational proof-of-concept than a fully weaponized exploit. The client logic uses Python’s standard `urllib` stack with optional SSL verification disabling, Basic Authorization headers, JSON/ODATA-style headers, and support for request digest handling (`X-RequestDigest`) typical of SharePoint state-changing operations. Based on the visible code and README, the exploit authenticates to a SharePoint site, obtains any required anti-CSRF/request digest token, and then attempts to exploit list item update functionality in a specified `SiteName/ListName` path to deliver the serialized payload. The CLI requires target URL, username, password, and site/list path, and optionally accepts a command, proxy, timeout, SSL verification, and a `--shell` mode. Capabilities: authenticated remote command execution against a SharePoint server via crafted serialized data delivered through list item update operations. The default command is `whoami /all`, but the operator can supply arbitrary commands. The payload is hardcoded in structure but customizable in command content, which supports an OPERATIONAL maturity assessment rather than pure POC or framework-grade weaponization. Fingerprintable observables are limited. The repository contains example target and proxy URLs in the README (`https://sharepoint.target.com`, `http://127.0.0.1:8080`), a reference URL to NVD, and author contact/branding URLs. Within the exploit code, the most relevant execution artifacts are `cmd.exe` and `/bin/bash`, which are the process launch targets embedded in the payload. The exact SharePoint REST/API paths are not fully visible in the provided truncated content, but the code clearly constructs requests by concatenating a user-supplied base target with internal request paths and uses SharePoint-specific headers and digest tokens. Overall, this repository appears to be a real exploit script rather than a detection tool or fake destructive sample. However, because the visible payload generation is explicitly described as a simplified simulation of a true .NET deserialization chain, the code should be treated as a plausible exploit PoC/operational script whose success may depend on omitted functions and target-specific SharePoint behavior.amnsecurity · Disclosed Jul 7, 2026 · python · markdown · network · webOperationalsharepoint-2026-pocRepository contains a documented proof-of-concept and detection notes for SharePoint /_trust WS-Federation SecurityContextToken deserialization leading to unauthenticated RCE and machine-key theft. Structure is small and focused: README and index.html provide the writeup; detection/hunting.md contains defender-oriented hunting guidance; artifacts/ contains redacted example telemetry; scripts/ contains the actual exploit code. The main exploit capability is in scripts/cve-2026-58644_oob_param.ps1. It is a parameterized PowerShell exploit that builds a PowerShell payload, base64-encodes it for -EncodedCommand, invokes ysoserial.net to generate a BinaryFormatter gadget (default TypeConfuseDelegate), wraps the raw gadget bytes with System.IdentityModel.DeflateCookieTransform, embeds that into a crafted WS-Federation RequestSecurityTokenResponse, and POSTs it to $Target/_trust/default.aspx with wa=wsignin1.0. Capabilities include arbitrary command execution, optional HTTP callback/beaconing, optional file drop, optional diagnostic exfiltration, proxy support, and optional direct powershell execution via --rawcmd to avoid cmd.exe in the process tree. The second exploit, scripts/cve-2026-58664_machinekeys.ps1, is a two-stage PowerShell exploit for in-process machine-key disclosure. It generates two ysoserial payloads: a preamble using ActivitySurrogateDisableTypeCheck and a main payload using ActivitySurrogateSelectorFromFile to compile embedded C# code (KeyDump) inside w3wp.exe. That C# reflects into System.Web.Configuration.MachineKeySection, extracts ValidationKey/DecryptionKey and related settings, clears the HTTP response, and writes the values back between sentinel markers. This is more stealthy than the OOB RCE path because it avoids child process creation and external beaconing. Overall, this is a real exploit repository rather than a detector-only repo. It is not part of a major exploitation framework. The code is operational but still PoC-style: payloads are customizable through parameters, but execution depends on an external ysoserial.net binary and a vulnerable SharePoint deployment. The most fingerprintable target artifact across both scripts is POST traffic to /_trust/default.aspx carrying wa=wsignin1.0 and a RequestSecurityTokenResponse/SecurityContextToken body.WismanSec · Disclosed Jul 26, 2026 · powershell · csharp · web · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationSharepoint Enterprise Serverapplication
Microsoft CorporationSharepoint Serverapplication
Microsoft CorporationSharepoint Server 2016application
Microsoft CorporationSharepoint Server 2019application
FAQ

Frequently asked questions

Is CVE-2026-45659 exploited in the wild?
Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jul 1, 2026.
Is there a public exploit for CVE-2026-45659?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-45659, the earliest disclosed Jul 7, 2026.
Is there a patch for CVE-2026-45659?
Apply Microsoft's security updates to every affected server in the SharePoint farm. Minimum fixed builds for this vulnerability are 16.0.5552.1002 for SharePoint Server 2016 and SharePoint Enterprise Server 2016, 16.0.10417.20128 for SharePoint Server 2019, and 16.0.19725.20280 for SharePoint Server Subscription Edition.
What products are affected by CVE-2026-45659?
Microsoft Corporation Sharepoint Server, Microsoft Corporation Sharepoint Server 2016, Microsoft Corporation Sharepoint Server 2019, and Microsoft Corporation Sharepoint Enterprise Server.
How severe is CVE-2026-45659?
CVE-2026-45659 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 80.2% (100th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

354 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+49 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware13Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity140Community discussion across Reddit, Mastodon, and other social sources.