Skip to content
Microsoft SharePoint
ProductUS

Microsoft SharePoint

Microsoft collaboration platform; spoofing zero-day CVE-2026-32201 actively exploited at the time of the April 2026 Patch Tuesday release.

Last refreshed: 17 April 2026 · Appears in 1 active topic

Key Question

Was SharePoint being actively hacked on the same day Microsoft released the patch?

Timeline for Microsoft SharePoint

#117 Apr

Handala wipes 200,000 devices at Stryker

Cybersecurity: Threats and Defences
#117 Apr

GRU hijacks home routers for M365 logins

Cybersecurity: Threats and Defences
View full timeline →
Common Questions
Is SharePoint being actively hacked in 2026?
Yes. CVE-2026-32201, an Improper Input Validation vulnerability in SharePoint Server, was added to CISA's Known Exploited Vulnerabilities catalogue in April 2026 as actively exploited at the time of Microsoft's Patch Tuesday disclosure.Source: CISA KEV

Background

CVE-2026-32201, an Improper Input Validation vulnerability in Microsoft SharePoint Server, was added to the CISA Known Exploited Vulnerabilities catalogue as actively exploited at the time of the April 2026 Patch Tuesday release. The simultaneous discovery-and-exploitation pattern means organisations that had not patched by Patch Tuesday were already exposed at the moment Microsoft disclosed the vulnerability.

Microsoft SharePoint is the company's enterprise document management and collaboration platform, used by hundreds of thousands of organisations for intranet portals, document libraries and workflow automation. Its deep integration with Microsoft 365 and Active Directory makes it a high-value target: a SharePoint vulnerability with Server-side request forgery, authentication bypass or code-execution characteristics can provide a pivot into the broader M365 tenant and on-premises AD environment.

For enterprises on SharePoint Server (as opposed to SharePoint Online), the April CVE is a patch-now obligation under KEV for federal agencies and a high-priority item for enterprise patch teams. The active-at-disclosure pattern also appears in the F5 reclassification story in this update: defenders are consistently in a reactive position against vulnerabilities being exploited before or simultaneously with patch availability.