The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record
Check your installed SharePoint Server version(s) (2016, 2019, Subscription Edition) against the fixed versions listed below.
If you are on an affected version, schedule and apply the Microsoft update for CVE-2026-64921 as soon as possible.
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.
After patching, verify SharePoint reports the expected new build number and do a quick access/permissions review for admin and high-privilege accounts.
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
What is it
Think of SharePoint like the office building where documents are stored. This vulnerability is like a door guard problem that can let someone move from “allowed visitor” to “trusted staff” by gaining higher permissions. Once that happens, they may be able to view or manage more than they should—and they can potentially disrupt normal operations.
Who is affected
This matters if you run Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, or Microsoft SharePoint Server Subscription Edition (including “sharepoint server” deployments). The weakness is specifically about elevating privileges, so it targets organizations that rely on SharePoint for sensitive documents and business workflows.
This is primarily a risk when an attacker can reach the SharePoint environment and can get an authorized position (for example, credentials or access inside the environment are the likely starting point).
How urgent is it
This is RED because it’s a high-impact privilege-escalation issue in widely used SharePoint Server software, and Microsoft has already released fixed versions. Recent security attention also points to interest from the Lazarus group, increasing the practical risk.
Even though there’s no public exploit code on record and it’s not listed in CISA KEV, you should treat this as a serious patch-now item for any affected SharePoint deployment.
What to do — in detail
Confirm what you run
Identify whether your environment includes Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, or Microsoft SharePoint Server Subscription Edition.
Record the current SharePoint build/version number(s).
Check for exposure
Compare your build against the Microsoft fixed versions provided for CVE-2026-64921.
Consider a higher priority if SharePoint is reachable from the internet or if you have users/roles that an attacker could plausibly obtain (the vulnerability requires an authorized attacker according to the provided description).
Patch to a fixed version (the exact targets)
SharePoint Enterprise Server 2016: upgrade/fix to 16.0.5565.1001
SharePoint Server 2019: upgrade/fix to 16.0.10417.20198
SharePoint Server Subscription Edition (and “sharepoint server”): upgrade/fix to 16.0.19725.20522
Validate after patching
Verify SharePoint now shows the expected build number.
Re-check that critical admin/high-permission accounts have not gained unexpected privileges.
Temporary risk-reduction while patching (if you need time)
Reduce SharePoint’s exposure to the smallest possible network surface (limit inbound access).
Review and tighten access controls and privileged roles (least privilege), since the scenario involves an attacker already having an authorized position.
Monitor authentication and permission-related events closely for unusual changes (new admin assignments, permission escalations, or abnormal access patterns). If you see suspicious activity, isolate affected instances and escalate internally.
Timing
Follow Microsoft’s update guidance from their CVE-2026-64921 update page and apply within your next available maintenance window that supports these upgrades.
Technical context
CVE-2026-64921 is a CWE-306 elevation of privilege issue in Microsoft SharePoint Server. The weakness is described as missing authentication for a critical function, which can allow an authorized attacker to elevate privileges over the network (i.e., increasing their effective permissions beyond what they should have).
Findings summary relevant to operational risk:
Confirmed exploitation status: not listed in CISA KEV, and no public exploit code is recorded (no direct proof of widespread exploitation in the provided data).
Patch availability: Microsoft has released fixed builds for SharePoint Enterprise Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition (plus a corresponding “sharepoint server” fixed build mapped to the same target).
Public activity signals: security press has noted attention connected to the Lazarus group and the existence of a patch.
Attack characteristics (from the provided technical description/backstop and stated CVSS vector): network-based (AV:N), low attack complexity (AC:L), low privileges required (PR:L), and no user interaction (UI:N). The practical consequence is unauthorized privilege gain within the SharePoint authorization context, which can lead to confidentiality and integrity impact across SharePoint content and administration capabilities.
This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.