Pentesting
patch-tuesday
zero-day
vulnerabilities

April 2026 Patch Tuesday: Critical Vulnerabilities

Analysis of April 2026 Patch Tuesday: 168 CVEs, an actively exploited SharePoint zero-day, and a wormable TCP/IP RCE vulnerability.

SecraApril 16, 20268 min read

Microsoft's April 2026 Patch Tuesday stands out as one of the most consequential security updates of the year. With patches for 168 vulnerabilities, including two zero-days — one actively exploited in real-world attacks against SharePoint environments — and eight critical-severity flaws, organizations running Microsoft infrastructure face an urgent patching mandate. Attackers already have working exploits. The window to act is closing fast.

This article breaks down the most dangerous vulnerabilities in this patch cycle, explains their real-world impact on enterprise environments, and provides concrete technical guidance for protecting your infrastructure.

CVE-2026-32201: Actively Exploited SharePoint Zero-Day

The most urgent vulnerability in this cycle is CVE-2026-32201, a spoofing flaw in Microsoft SharePoint Server caused by improper input validation. An unauthenticated attacker can exploit this vulnerability over the network to compromise the confidentiality and integrity of data stored in SharePoint.

Microsoft has confirmed this CVE is being actively exploited in the wild. While its official severity rating is "Important" rather than "Critical," active exploitation makes it an emergency remediation target. SharePoint environments typically house internal documents, project data, shared credentials, and strategic business information — any compromise has direct business impact.

Immediate action: patch all SharePoint Server instances within 24-48 hours. If immediate patching is not feasible, monitor SharePoint access logs for anomalous authentication patterns and malformed requests. Consider restricting network access to SharePoint to authorized network segments only.

CVE-2026-33827: Wormable TCP/IP Remote Code Execution

From a purely technical standpoint, CVE-2026-33827 is the most dangerous vulnerability in this cycle. It is a remote code execution (RCE) flaw in the Windows TCP/IP stack that allows an unauthenticated remote attacker to execute arbitrary code without any user interaction.

This vulnerability is wormable — malware exploiting it can spread automatically from system to system without human intervention, similar to how WannaCry and EternalBlue operated. Affected systems are those with IPv6 and IPSec enabled, a standard configuration in modern corporate networks.

The attack vector is particularly dangerous because it operates at the network level. An attacker can compromise a system simply by sending malicious network packets. No authentication required, no user interaction needed, and the attack complexity is low.

Potential impact: mass propagation within corporate networks, automatic lateral movement, and cascading compromise of servers and workstations. This is precisely the type of vulnerability that Red Team exercises simulate to test an organization's resilience against full infrastructure compromise scenarios.

Recommendation: prioritize patching all exposed Windows systems. If immediate patching is not feasible, consider temporarily disabling IPv6 on systems where it is not strictly required and review firewall rules for inbound IPSec traffic.

CVE-2026-33824: IKE Remote Code Execution — CVSS 9.8

CVE-2026-33824 affects the Internet Key Exchange (IKE) Service Extensions in Windows and carries a CVSS score of 9.8 out of 10 — the highest possible for a remote code execution flaw. IKE is a core component of the IPSec protocol, widely used in corporate VPNs and secure point-to-point connections.

An unauthenticated remote attacker can exploit this vulnerability with low complexity and no user interaction, achieving arbitrary code execution on the target system with the privileges of the IKE service.

The risk is particularly elevated for organizations exposing IPSec-based VPN services to the internet — an extremely common configuration since the widespread adoption of remote work. An attacker who compromises the IKE service gains direct access to the organization's internal network.

Recommendation: verify whether your VPN concentrators or Windows servers with VPN roles are running the IKE service and apply the patch as a priority. Supplement with IDS/IPS detection rules for anomalous IKE traffic.

Beyond Microsoft: Fortinet and Adobe Also Affected

This patch cycle extends well beyond Microsoft. Other vendors have released critical updates with direct implications for enterprise security:

Fortinet — CVE-2026-35616 (FortiClient EMS): a critical vulnerability in FortiClient Enterprise Management Server that is actively exploited in real-world attacks. FortiClient EMS is the central endpoint management component in Fortinet environments — its compromise can give an attacker control over the entire fleet of managed devices. Organizations using Fortinet should treat this patch as an emergency.

Adobe Reader/Acrobat — Active zero-day: Adobe has patched a zero-day in Reader and Acrobat that was already being exploited, likely through malicious PDF documents distributed via email. This attack vector is one of the most effective in spear-phishing campaigns and affects virtually every organization.

Apache ActiveMQ Classic: a remote code execution vulnerability that went undetected for 13 years has been discovered and patched. This case underscores the importance of periodic security audits and Software Composition Analysis (SCA) as part of a secure development lifecycle (SSDLC) strategy.

Breakdown of All 168 Vulnerabilities

The distribution of Microsoft's 168 patched vulnerabilities reflects current threat landscape trends:

  • 93 Elevation of Privilege vulnerabilities — more than half of all fixes, indicating that attackers increasingly focus on lateral movement and privilege escalation within already-compromised systems.
  • 20 Remote Code Execution (RCE) vulnerabilities — including the critical flaws in TCP/IP, IKE, and Active Directory.
  • 21 Information Disclosure vulnerabilities — potentially usable for reconnaissance prior to more sophisticated attacks.
  • 13 Security Feature Bypass vulnerabilities — enabling evasion of existing security controls.
  • 10 Denial of Service vulnerabilities — capable of disrupting critical service availability.
  • 8 Spoofing vulnerabilities — including the SharePoint zero-day.

Affected products span a broad spectrum: Windows Kernel, TCP/IP, Active Directory, Microsoft Office (Word and Excel), SharePoint, Remote Desktop Client, Azure, SQL Server, Visual Studio Code, and even GitHub Copilot. Virtually no Microsoft environment is exempt from exposure.

How to Assess Your Real Exposure

Publishing patches is only the first step. The critical question is: how long have you been exposed, and have these vulnerabilities been exploited in your environment? Answering that requires going beyond reactive patching:

1. Updated asset inventory. You cannot patch what you do not know exists. Map all Windows systems, SharePoint instances, VPN/IKE services, Fortinet endpoints, and Adobe applications across your infrastructure. According to the NIST Cybersecurity Framework, asset inventory is the foundational pillar of any security program.

2. Vulnerability scanning. Run targeted vulnerability scans against this Patch Tuesday's CVEs to confirm which systems are affected. A penetration test goes further by validating whether these vulnerabilities are actually exploitable in your specific configuration.

3. Log review. Search for indicators of compromise (IoCs) associated with CVE-2026-32201 in SharePoint logs and CVE-2026-35616 in FortiClient EMS logs. Confirmed active exploitation means attackers are already using these exploits — your environment may have already been compromised.

4. Network segmentation. Verify that your networks are properly segmented to limit propagation of wormable threats like CVE-2026-33827. Microsegmentation is especially important in Active Directory environments, where compromise of a domain controller can mean total organizational compromise.

5. Attack simulation. A Purple Team exercise allows you to simulate exploitation of these vulnerabilities in a controlled environment, validate detection effectiveness, and train your defensive team to respond to real incidents based on these threats.

NIST Updates NVD Operations Amid Record CVE Growth

A relevant contextual development: on April 15, 2026, NIST announced changes to National Vulnerability Database (NVD) operations to address the explosive growth in CVEs, which increased 263% between 2020 and 2025. Going forward, NIST will prioritize analysis of vulnerabilities appearing in CISA's KEV (Known Exploited Vulnerabilities) catalog, software used within the federal government, and critical software as defined by Executive Order 14028.

This change has direct implications for organizations relying on the NVD for vulnerability management: turnaround times for complete analyses may vary based on the priority assigned to each CVE. Organizations should supplement their vulnerability intelligence with additional sources rather than depending exclusively on the NVD.

For organizations subject to regulations such as ENS or NIS2, which mandate active vulnerability management and incident notification, this context reinforces the need for mature governance, risk, and compliance (GRC) processes.

Patching Priorities and Action Plan

Based on the analysis above, here is our recommended prioritization:

Critical priority (patch within 24-48h):

  • CVE-2026-32201 — SharePoint Server (active zero-day)
  • CVE-2026-35616 — FortiClient EMS (active zero-day)
  • CVE-2026-33827 — Windows TCP/IP (wormable)
  • CVE-2026-33824 — Windows IKE (CVSS 9.8)
  • Adobe Reader/Acrobat (active zero-day)

High priority (patch within 1 week):

  • CVE-2026-33826 — Active Directory RCE
  • CVE-2026-33825 — Microsoft Defender EoP (publicly disclosed)
  • CVE-2026-33115 / CVE-2026-33114 — Microsoft Word RCE
  • CVE-2026-32157 — Remote Desktop Client RCE

Medium priority (patch within regular cycle):

  • Remaining vulnerabilities based on your environment's specific exposure.

Protect Your Organization with a Security Assessment

Patch Tuesdays like April 2026 demonstrate that organizational attack surfaces are constantly expanding. Patching is necessary but not sufficient — you need to validate that your controls work, that you have not been compromised, and that your team is prepared to respond.

At Secra, we help organizations of all sizes assess their real security posture through security audits, penetration testing, and attack simulation exercises. If you want to understand how exposed your infrastructure is to these critical vulnerabilities, request a free initial assessment through our contact page. Our team of offensive security specialists will analyze your environment and provide a prioritized action plan tailored to your reality.

Share article

👋Hi! Have any questions? Write to us, we reply in minutes.

Open WhatsApp →