cve.bz

CVE-2026-32201 Microsoft SharePoint Server Improper Input Validation Vulnerability

6.5 mediumKEVEPSS 44%

Medium (6.5) in Microsoft SharePoint Server. In CISA KEV since 2026-04-14. EPSS 44% estimated probability of exploitation activity in the next 30 days.

On this page
Improper input validation in Microsoft Office SharePoint allows an unauthorized attacker to perform spoofing over a network.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
44% (unchanged from 43% a week ago; 43% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-04-14, due 2026-04-28
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: partial, assessed 2026-04-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32201 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32201?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32201?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32201 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-32201

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-32201](https://cve.bz/cve/badge/CVE-2026-32201.svg)](https://cve.bz/cve/CVE-2026-32201)

HTML:

<a href="https://cve.bz/cve/CVE-2026-32201"><img src="https://cve.bz/cve/badge/CVE-2026-32201.svg" alt="CVE-2026-32201"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft SharePoint Enterprise Server 2016from 16.0.0 before 16.0.5548.1003
Microsoft SharePoint Server 2019from 16.0.0 before 16.0.10417.20114
Microsoft SharePoint Server Subscription Editionfrom 16.0.0 before 16.0.19725.20210

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • B1tBit/CVE-2026-32201-exploit 1 star, Python, created
    A spoofing vulnerability exists in Microsoft SharePoint Server due to improper input validation. An unauthenticated attacker can send a spe…

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON