Loading vulnerability…
CVE-2026-32201 is an improper input validation vulnerability in Microsoft SharePoint Server that allows an unauthenticated attacker to perform spoofing over a network. Improper validation of user-supplied input enables impersonation of a legitimate entity, potentially exposing sensitive information and permitting limited changes to disclosed information. The vulnerability was exploited as a zero-day before Microsoft released a fix in April 2026 and was added to CISA's Known Exploited Vulnerabilities catalog on April 14, 2026.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python proof-of-concept exploit script and a README. The main file, CVE-2026-32201-exploit.py, is a standalone CLI tool using requests, argparse, sys, and urllib.parse.urljoin. Its workflow is simple: first fingerprint the target by issuing a GET request to /_layouts/15/start.aspx and checking for a 200 response containing the string 'SharePoint'; if detected, it sends a crafted POST request to a configurable endpoint, defaulting to /_layouts/15/notify.aspx. The POST body includes recipient, subject, message, and sender_override, where sender_override is treated as the allegedly vulnerable parameter enabling spoofed sender identity. The script prints status code, response length, a response snippet, and basic success indicators such as 'success' or 'sent' in the response body. The exploit is network/web-based, unauthenticated in design, and intended to spoof SharePoint notifications rather than achieve code execution. The README expands on intended use, affected SharePoint versions, and possible operator customization, including arbitrary message content and endpoint fuzzing. Overall, this is a small operational PoC for testing a claimed SharePoint spoofing/input-validation issue, not a framework module and not merely a detector.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
169 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A recent vulnerability potentially included in the Storm-2603/Longlegs exploitation arsenal; the article provides no technical details or confirmed exploitation evidence for this specific CVE.
An unspecified Microsoft SharePoint Server vulnerability reported as actively exploited to compromise Internet-exposed on-premises SharePoint instances.
A Microsoft SharePoint Server vulnerability discussed as one of three flaws being actively exploited, enabling serious post-compromise outcomes including authentication bypass, code execution, credential/key theft, persistence, and malware deployment.
A Microsoft SharePoint Server spoofing vulnerability, likely related to XSS, mentioned only as historical background and noted as added to CISA KEV.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.