Automated Threat Modeling

Quick Look: Microsoft SharePoint CVE-2026-124223 Deserialization Leading to Remote Code Execution

A brief summary of CVE-2026-124223, a flaw in how SharePoint Server Subscription Edition deserializes untrusted data that lets a low-privilege authenticated attacker execute code on the server. It covers the affected builds, the November 2026 KB5002945 fix, and why the CVE was missing from the KB article.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-16

Quick Look: Microsoft SharePoint CVE-2026-124223 Deserialization Leading to Remote Code Execution

Introduction

On an unpatched SharePoint Server Subscription Edition farm, any authenticated user with only low privileges could send specially formatted input to a vulnerable API. SharePoint would deserialize that input unsafely, and the result could be code execution on the SharePoint server. Microsoft shipped the fix on November 10, 2026 in KB5002945 but published the advisory on November 16. Teams that match patches against the CVE lists in KB articles may not have linked this issue to an update they had already deployed.

Technical information

Root cause

CVE-2026-124223 is classified as CWE-502, deserialization of untrusted data. According to MSRC, an attacker could exploit vulnerable SharePoint APIs through unsafe deserialization. Microsoft states two conditions for exploitation: access to a susceptible API on an affected SharePoint version, and specially formatted input sent to that API. This can result in remote code execution on the SharePoint Server.

Microsoft has not named the vulnerable API or endpoint, the serializer involved, or the input format, so we do not speculate about them here. SharePoint is closed source, and there is no public diff or commit to inspect. For .NET deserialization bugs, a fix usually takes one of two forms: the server stops deserializing data it cannot trust, or it limits which types may be rebuilt from that data. Microsoft has not said which approach it took for this CVE.

CVSS breakdown

The CNA (Microsoft) score is 8.8 High under CVSS 3.1:

MetricValue
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

NVD was still undergoing enrichment and had not supplied its own base score. It listed the CNA score of 8.8 High.

Attack flow

Based on the MSRC description, the exploitation path is:

  1. The attacker holds an authenticated account on the SharePoint farm. Only low privileges are required.
  2. The attacker reaches a susceptible SharePoint API over the network.
  3. The attacker submits specially formatted input to that API. No interaction from any other user is needed.
  4. SharePoint deserializes the attacker-controlled data unsafely.
  5. Code executes in the SharePoint server environment.

The advisory does not specify what an attacker could access or change after gaining execution. The High ratings for confidentiality, integrity, and availability reflect the severity of server-side code execution.

Exploitation status

The MSRC advisory reports:

  • Exploited: No
  • Publicly disclosed: No
  • Exploitability assessment: Exploitation Less Likely
  • Exploit code maturity: Unproven
  • Remediation level: Official Fix

No threat actor or campaign is associated with this CVE in the cited sources. These values are Microsoft's assessment at publication and do not rule out future exploitation.

Patch information

Microsoft fixed CVE-2026-124223 in the November 10, 2026 security update for SharePoint Server Subscription Edition, KB5002945. After installation, the farm is on build 16.0.20326.20278. The MSRC Security Updates table has one row for this CVE: Microsoft SharePoint Server Subscription Edition, linking to KB 5002945, a Download Center package, and build 16.0.20326.20278.

Why KB5002945 does not list this CVE

KB5002945 lists 24 other SharePoint and Word CVEs, including the related SharePoint remote code execution issues CVE-2026-120000 and CVE-2026-109464, but not CVE-2026-124223.

Microsoft published this CVE on November 16, 2026, six days after the update shipped. The MSRC revision note says the CVE was fixed by the November 2026 updates but was "inadvertently omitted from the November 2026 Security Updates." Microsoft describes this as an informational change only. The fix was in the package all along, so farms that already installed the November update need no further action.

Package details

  • Cumulative uber package: Subscription Edition updates ship as a single unified package containing both language-independent and language-dependent fixes. KB5002945 replaces the previous security update, KB5002927.
  • File: uber-subscription-kb5002945-fullfile-x64-glb.exe
  • SHA256: 31B944695F41590F52167E59EC3BF09DEA0590C9546C08D681607CE80E14F0E6
  • Sources: Microsoft Update, the Microsoft Update Catalog (search KB5002945), or the Download Center (id=108898). Stefan Gossner of Microsoft notes that the Download Center serves the same package whichever language you select.

Installation requirements

  • The release version of SharePoint Server Subscription Edition must already be installed.
  • Farms that use SharePoint Workflow Manager must install KB5002799 before this cumulative update.
  • Installing the binaries is not enough. Run the SharePoint Products Configuration Wizard, or psconfig, on every server in the farm. Until that step finishes, the farm has not fully moved to the fixed build.
  • To verify, check the build. A farm at 16.0.20326.20278 or later has the fix. Any earlier 16.0.x build of Subscription Edition does not.

Regression to be aware of

The same November package changed email behavior to prevent spoofing. Previously, when the current user had no email address, SharePoint fell back to sending email as the system account. The update removed that fallback.

Gossner's post reports that some workflows now fail with an error stating that the sender email address could not be resolved. This is most common in workflow logic running in an app context (AppStep). Microsoft's workaround is the farm debug flag 60110.

This regression is unrelated to the deserialization fix. We mention it so the behavior change is not mistaken for a broken patch.

Affected systems and versions

ProductPlatformAffected versionsFixed build
Microsoft SharePoint Server Subscription Editionx6416.0.0 up to, but not including, 16.0.20326.2027816.0.20326.20278 (KB5002945)

The MSRC Security Updates table lists no other SharePoint product for this CVE. Exploitation requires an authenticated account with network access to the vulnerable API.

Vendor security history

KB5002945 also addresses 24 other SharePoint and Word CVEs, including two related SharePoint remote code execution issues, CVE-2026-120000 and CVE-2026-109464.

MSRC states that it works with product and engineering teams and the global security research community to identify, understand, and respond to vulnerabilities, coordinate fixes, and drive mitigations.

For this CVE, the fix shipped on schedule, but the advisory followed six days later because of a listing omission that Microsoft acknowledged in its revision note. The cited sources do not support broader conclusions about Microsoft's comparative security record.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization