CVE Tools

CVE-2026-64921

Microsoft SharePoint Server Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 59th 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 your installed SharePoint Server version(s) (2016, 2019, Subscription Edition) against the fixed versions listed below.
  2. If you are on an affected version, schedule and apply the Microsoft update for CVE-2026-64921 as soon as possible.
  3. Upgrade to one of these fixed versions: SharePoint Enterprise Server 2016 → 16.0.5565.1001; SharePoint Server 2019 → 16.0.10417.20198; SharePoint Server Subscription Edition → 16.0.19725.20522.
  4. After patching, verify SharePoint reports the expected new build number and do a quick access/permissions review for admin and high-privilege accounts.

What it is

From the CVE record

Missing authentication for critical function in Microsoft Office SharePoint allows an authorized attacker to elevate privileges over a network.

In plain language

Written by AI from the record

CVE-2026-64921 is a serious SharePoint Server security hole that lets an attacker gain higher permissions over the network; if you run Microsoft SharePoint, you should patch promptly, especially if it’s reachable from outside your organization.

CVE-2026-64921 is an elevation of privilege weakness (CWE-306) in Microsoft SharePoint Server where improper handling of authentication for a critical function can let an authorized attacker increase privileges over the network.

If you're affected

  • Site takeover with higher permissions
  • Data access beyond intended roles
  • Potential service disruption
  • Compromise of business operations

Exploitation

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

EPSS59th
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

0.9% chance of exploitation activity in the next 30 days, which ranks it in the 59th 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