Skip to main content

Microsoft Patches Critical SharePoint Remote Code Execution Flaws

Microsoft's November 2026 update closes SharePoint remote code execution bugs that need a login. Here is what admins and students should know.

By Mittapalli Sriram
Published: Nov 21, 2026
4 min read
👁️ 18 Unique Views
Microsoft Patches Critical SharePoint Remote Code Execution Flaws
Premium Insight

Why It Matters

SharePoint servers hold shared files and company workflows, so a flaw that lets a logged-in user run code on the server can matter anywhere. Microsoft's November update fixes such flaws, and the March 2026 case shows that a flaw rated less likely to be exploited can later be exploited. Any organisation that runs its own SharePoint servers should check its patch level.

Microsoft has fixed several SharePoint remote code execution flaws in its November 2026 update for SharePoint Server Subscription Edition. Remote code execution means an attacker can run their own commands on a server over a network, from far away. Imagine a visitor whose badge opens only one office door. A flaw like this lets that badge start machines across the whole building.

What Happened in the November Update

Microsoft released security update KB5002945 on 10 November 2026. Its support article says the update fixes several types of flaws, including remote code execution, and links to 24 advisories. The fixed build number is 16.0.20326.20278.

One flaw, CVE-2026-124223, was listed later. A CVE is a public ID number for a known security flaw. Microsoft's advisory, dated 16 November, says the fix was already in the November updates but the entry was left out by mistake. Customers who installed them don't need to do anything more.

How It Works: Unsafe Data and Permissions

Several flaws involve deserialization of untrusted data. Deserialization means a program rebuilds an object from stored data, like putting furniture together from a box. If someone tampers with the box, you get a harmful result.

In its advisory for CVE-2026-124223, Microsoft says an attacker has to send specially formatted input to a vulnerable API, which is a door that lets programs talk to SharePoint. The advisories also say the attacker needs an account. For CVE-2026-110044, Microsoft says site member permissions are enough. For CVE-2026-109499, it says the Design permission is enough.

Latest Developments: Real SharePoint Attacks in 2026

The clearest recent case is CVE-2026-20963. In advisory 2026-004, dated 25 March 2026, CERT-EU (the cyber response team for European Union bodies) says Microsoft raised the severity score on 17 March and noted that no login is needed. CERT-EU adds that CISA, the US cyber agency, listed the flaw as exploited on 18 March.

SecurityWeek reported that Microsoft had earlier rated exploitation as less likely, and that no public details of the attacks existed.

Future Potential, Applications, Impact and Business

Looking ahead, Microsoft's support article names two planned changes. SharePoint will start blocking remote event receivers registered without an application identity in the March 2027 public update. The 13 July 2027 update will remove SharePoint 2010 workflows and InfoPath Forms Services, which Microsoft says reached end of support on 14 July 2026.

None of the sources we opened describe future uses of these flaws, forecast new attacks, or estimate effects on jobs or markets. Those parts are not known yet. CERT-EU only advises precautions like rotating ASP.NET machine keys.

Our Analysis: Challenges and What It Means for India

This section is our own thinking, not the sources'. The main challenge is delay. Organisations patch their own SharePoint servers, and the March 2026 case shows that a flaw rated less likely to be exploited can later be exploited.

None of the sources we opened confirm any attack or effect in India. Still, Indian offices, colleges and software firms running SharePoint Server Subscription Edition should check that the November update is installed.

A patch only protects a server once someone installs it. The lesson is simple: check the build number, apply updates early, and don't wait for an attack report before acting.

Found this analysis insightful?

Share with colleagues, engineers, and your network.

Link copied to clipboard!