CriticalCVE-2026-50522

    Microsoft SharePoint Remote Code Execution Vulnerability (CVE-2026-50522)

    Published Last modified In CISA KEV since Sources: CERT-EU, SingCERT, NCSC NZ, pwn.watch, CVE.org, Msrc Update Guide, BSI

    What is affected, what to do

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

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft SharePoint Enterprise Server 2016 to version 16.0.5561.1001, Microsoft SharePoint Server 2019 to version 16.0.10417.20175, Microsoft SharePoint Server Subscription Edition to version 16.0.19725.20434. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft SharePoint Enterprise Server 2016 lt 16.0.0..16.0.5561.1001
    • Microsoft SharePoint Server 2019 lt 16.0.0..16.0.10417.20175
    • Microsoft SharePoint Server Subscription Edition lt 16.0.0..16.0.19725.20434
    Fixed in
    • Microsoft SharePoint Enterprise Server 2016 16.0.5561.1001
    • Microsoft SharePoint Server 2019 16.0.10417.20175
    • Microsoft SharePoint Server Subscription Edition 16.0.19725.20434

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CERT-EU, SingCERT, NCSC NZ, pwn.watch, CVE.org, Msrc Update Guide, BSI

    3.0 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 87.4

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    231.04 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), ANSSI / CERT-FR, NCSC NZ How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    3.0 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    87.4
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-502

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable without authentication or user interaction and yields full code execution in the SharePoint worker process, which places it at the top of the severity scale. The CVSS vector still marks exploit maturity as unproven, but KEV listing overrides that, and exploitation likelihood is assessed as well above average. Earlier SharePoint deserialization bugs were mass-exploited within days against exposed on-prem farms in government, energy, manufacturing and the mid-market. Typical follow-on activity was webshell drops, machine-key theft and lateral movement into Active Directory. CISA does not currently flag ransomware use. Even so, treat internet-facing farms as an emergency requiring patch-or-disconnect today, and patch internal-only farms within days, followed by key rotation in both cases.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Enumerate every on-premises SharePoint Server farm on the 16.0 build line and record its build (Get-SPFarm | Select BuildVersion). The context explicitly lists build 16.0.19725.20434 as affected. Prioritise internet-reachable farms on TCP 80/443, including those published through a reverse proxy.
      • Patch: The context indicates an official fix is available (RL:O). Patch available from the vendor — look up the exact version in the vendor advisory. Install the update on every server in the farm, then run PSConfig.exe -cmd upgrade -inplace b2b -wait or the Configuration Wizard.
      • Reduce exposure: If a farm cannot be patched today, block external access at the perimeter. Alternatively, restrict access to VPN or a pre-authenticating Zero Trust proxy.
      • Rotate keys: After patching, rotate the ASP.NET machine keys (Set-SPMachineKey -WebApplication <URL>, then Update-SPMachineKey -WebApplication <URL>), and run iisreset on all farm servers. SharePoint deserialization intrusions routinely steal the ValidationKey and DecryptionKey. Without rotation, attackers can keep abusing signed ViewState even on a patched farm.
      • Compromise assessment: Before returning exposed servers to normal service, hunt for webshells and anomalous w3wp.exe child processes (see Detection rules). On any hit, isolate the host, preserve forensic images, and start NIS2/BSIG incident reporting (24 h early warning).
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place SharePoint front-ends in a dedicated DMZ or application zone. Default-deny internet egress from SharePoint and SQL servers to cut off payload staging and C2 traffic.
      • Endpoint hardening: Enable SharePoint AMSI integration, preferably in Full Mode, backed by Microsoft Defender Antivirus or an AMSI-capable EDR. Enable ASR rules, in particular "Block process creations originating from PSExec and WMI commands". Configure EDR policy to block, or at minimum alert on, child processes spawned by w3wp.exe.
      • WAF/IPS: Block unauthenticated POSTs to /_layouts/15/*.aspx that carry oversized __VIEWSTATE values or Base64 blobs with .NET gadget signatures. Examples are AAEAAAD///// (the BinaryFormatter header) or TypeConfuseDelegate and ObjectDataProvider in the decoded body. Watch for spoofed Referer headers pointing to /_layouts/SignOut.aspx. Enable vendor IPS signatures for this CVE as soon as they ship.
      • IAM/least privilege: The IIS application pool identity and the farm account must not hold local admin rights or Domain Admin membership. Trim SQL permissions to the minimum required and enable Credential Guard on farm servers.
      • Integrity monitoring: Apply FIM to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\ and to the IIS site web.config files.
    3. Runbook step 3

      Detection rules

      • EDR/Sysmon EID 1 or Security 4688: w3wp.exe spawning cmd.exe, powershell.exe, pwsh.exe, csc.exe, certutil.exe or rundll32.exe. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "w3wp.exe" and FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","csc.exe","certutil.exe").
      • Sysmon EID 11 (FileCreate): New .aspx or .ashx files under ...\16\TEMPLATE\LAYOUTS\ or in IIS webroots, written by w3wp.exe or powershell.exe. Sigma shape: Image|endswith: '\w3wp.exe' and TargetFilename|contains: '\TEMPLATE\LAYOUTS\' and TargetFilename|endswith: '.aspx'.
      • IIS access logs: POSTs to /_layouts/15/ from external IPs with no authenticated user (cs-username = -), followed by GETs to previously unseen .aspx files. SPL: index=iis cs_method=POST cs_uri_stem="/_layouts/15/*" cs_username="-" | stats count by c_ip, cs_uri_stem.
      • PowerShell logging (EID 4104) and AMSI/Defender (EID 1116/1117): Script blocks that touch System.Web.Configuration.MachineKeySection or dump the ValidationKey or DecryptionKey, plus AMSI detections attributed to w3wp.exe.
      • Network (Zeek/Suricata): Outbound connections from SharePoint servers to external destinations other than Microsoft update endpoints, especially immediately after suspicious POST bursts.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

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

    Source: certeu_advisory, CSA/SingCERT, NCSC NZ (CC BY 4.0), pwn.watch, cvelistv5, Microsoft Security Update Guide, CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), BSI WID Portal, BSI CSAF

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftMicrosoft SharePoint Enterprise Server 2016
    • 16.0.0 – < 16.0.5561.1001
    • 16.0.5561.1001
    MicrosoftMicrosoft SharePoint Server 2019
    • 16.0.0 – < 16.0.10417.20175
    • 16.0.10417.20175
    MicrosoftMicrosoft SharePoint Server Subscription Edition
    • 16.0.0 – < 16.0.19725.20434
    • 16.0.19725.20434
    microsoftsharepoint_server
    • 2019
    • 2016
    • < 16.0.19725.20434
    • —
    • —
    • 16.0.19725.20434

    Vendors and products

    Weakness classes (CWE)

    • CWE-502Deserialization of Untrusted Data

      Base

      The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

      Entry at MITRE CWE-502

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    NCSC NZCVE-2026-58644 and CVE-2026-50522 affecting SharePoint Server (opens in a new tab)NCSC NZactively exploited
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2026-ALE-008 – Multiples vulnérabilités dans Microsoft Sharepoint (clôturée 2026-09-22) (opens in a new tab)cert.cyber.gouv.fractively exploited
    PoC-in-GitHub (nomi-sec)sharepoint-2026-poc (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-50522 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-50522 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-50522 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2026-50522 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • Microsoft Security Update GuideMicrosoft SharePoint Remote Code Execution VulnerabilityVendor advisory, Patch, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-50522government-resource
    • cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2026-ALE-008 – Multiples vulnérabilités dans Microsoft Sharepoint (clôturée 2026-09-22)cert-fr
    • pwn.watchpwn.watch: Microsoft SharePoint: Microsoft SharePoint Deserialization of Untrusted Data Vulnerability pwn-watch
    • NVD (NIST)NVD: CVE-2026-50522pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    • JPCERT/CCJPCERT/CC JPCERT-AT-2026-0020: Microsoft Releases July 2026 Security Updatesjpcert

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-50522","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-22T20:45:10.104482Z"}
      {"id":"CVE-2026-50522","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-13T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-07-22
      Due Dateadded
      —
      2026-07-22
      Required Actionadded
      —
      2026-07-22
      Vulnerability Nameadded
      —
      2026-07-22

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    3. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-50522","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-13T00:00:00+00:00"}
      {"id":"CVE-2026-50522","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-22T20:45:10.104482Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    4. Record modifiedCISA ADP

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-50522

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-50522
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-50522"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-50522.svg?lang=en" alt="CVE-2026-50522 – NEOSEC Intel" height="20"></a>