CVE-2026-50522: Microsoft SharePoint Deserialization of Untrusted Data Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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

Description quoted from the CVE record (assigned by microsoft, published 2026-07-14).

Weakness: CWE-502: Deserialization of Untrusted Data

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-07-22
US federal deadline
2026-07-25
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-10084, EUVD-2026-43767, GHSA-ww8x-9jc5-9v7f, ZDI-26-412, ZDI-26-413

VEDAS cluster: VEDAS:FOXTROTFRANCE

Exploit Observer links 4 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (4)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (2)

Vulnerability databases and vendor advisories (5)

Catalogue entries, not exploit evidence.

News (2)

11 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.030
some chance of attack soon
VEDAS
0.980
strong exploit evidence
On CISA KEV
Yes, since 2026-07-22
Detection rule
None yet
EPSS (chance of attack)
100.1CVE-2026-50522 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-50522 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Microsoft Microsoft SharePoint Enterprise Server 2016from 16.0.0 before 16.0.5561.1001Not stated
Microsoft Microsoft SharePoint Server 2019from 16.0.0 before 16.0.10417.20175Not stated
Microsoft Microsoft SharePoint Server Subscription Editionfrom 16.0.0 before 16.0.19725.20434Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft sharepoint_server, microsoft_corp microsoft_sharepoint_enterprise_server_2016, microsoft_corp microsoft_sharepoint_server_2019, microsoft_corp microsoft_sharepoint_server_subscription_edition.

How to fix it

Fixed versions stated in the CVE record: 16.0.5561.1001, 16.0.10417.20175, 16.0.19725.20434.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset’s internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

Government sources

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.