CVE Tools

CVE-2026-66808

Microsoft SharePoint Server Remote Code Execution Vulnerability

No known exploitation. EPSS puts it in the 80th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check which Microsoft SharePoint Server version you run and whether it’s below the fixed versions for CVE-2026-66808.
  2. If your SharePoint version is not yet fixed, download and install the vendor update that fixes CVE-2026-66808.
  3. After updating, verify the SharePoint build/version matches the fixed target for your edition.
  4. Review authentication logs for suspicious successful logins to SharePoint accounts, since exploitation requires authorized credentials.

What it is

From the CVE record

Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.

In plain language

Written by AI from the record

CVE-2026-66808 is a SharePoint Server bug that lets an attacker with a basic login run commands on your server over the network, and it is reachable in default setups—if you use SharePoint Server 2016/2019/Subscription Edition, you should patch.

CVE-2026-66808 is a remote code execution issue caused by improper handling of serialized/untrusted data in Microsoft SharePoint Server; it can be triggered over the network by an attacker using low-privilege authenticated access and crafted data that causes the server to execute unintended commands.

If you're affected

  • Full server takeover
  • Malware deployment risk
  • Business disruption
  • Data theft from SharePoint

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS80th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

2.0% chance of exploitation activity in the next 30 days, which ranks it in the 80th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 4 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store