Critical
Windows IKEv2 Remote Code Execution
CVE-2026-33824 · CVSS 9.8 · Unauthenticated, zero interaction
An unauthenticated attacker can trigger remote code execution in the Windows IKEv2 service without user interaction. The vulnerability requires no privileges and is network-exploitable — CVSS 9.8. Affects all currently supported Windows Server versions. PoC circulating in private exploit markets as of April 22.
Action: Patch or firewall-restrict IKE ports before April 29 deadline.
Critical
Microsoft SharePoint Zero-Day — Actively Exploited
CVE-2026-32201 · CISA KEV — patch deadline April 28
A SharePoint Server zero-day is being actively exploited in the wild. CISA added this to the Known Exploited Vulnerabilities catalog with a mandatory federal remediation deadline of April 28, 2026. Attackers are leveraging the flaw for authenticated RCE on on-premises SharePoint farms. Cloud SharePoint Online customers are not affected — patched server-side by Microsoft.
Action: On-prem SharePoint — patch by April 28 (CISA KEV deadline).
High
CISA KEV Update — Samsung MagicINFO, SimpleHelp, D-Link DIR-823X
CISA KEV Addition — April 24, 2026
CISA added four actively exploited vulnerabilities to the KEV catalog on April 24. Samsung MagicINFO Server RCE (CVE-2025-4632, CVSS 9.8) is the most severe — unauthenticated attackers can write files and execute commands. SimpleHelp RMM path traversal (CVSS 7.5) is being leveraged for persistent access. D-Link DIR-823X firmware has a command injection flaw exploited by Mirai-variant botnets.
Action: Audit environment for Samsung MagicINFO, SimpleHelp RMM, and D-Link DIR-823X.
Critical
MCP Protocol Design Flaw — 7,000+ Servers Affected, Anthropic Declines to Patch
10 CVEs assigned · 150M+ downloads · Unauthenticated RCE potential
Security researchers disclosed 10 CVEs targeting the Model Context Protocol (MCP) — the standard used by Claude, Cursor, Windsurf, and dozens of AI agent frameworks. The flaws allow unauthenticated code execution, tool poisoning, and data exfiltration across 7,000+ MCP servers with 150M+ aggregate downloads. Anthropic acknowledged the findings but stated the issues are "by design" and declined to issue a patch at the protocol level, placing remediation responsibility on individual server implementers.
Action: Inventory all MCP servers, enforce auth, disable unnecessary MCP endpoints.
Critical
Azure MCP Server Authentication Bypass
CVE-2026-32211 · CVSS 9.1 · No authentication required
The official Azure MCP Server has a critical auth bypass flaw (CVSS 9.1) that allows unauthenticated actors to invoke MCP tools with full Azure API access. An attacker with network access to the MCP server can issue arbitrary Azure control-plane commands — creating resources, exfiltrating secrets, and potentially escalating to tenant-level access. The flaw exists due to missing token validation in the MCP tool dispatch handler.
Action: Update Azure MCP, rotate credentials, review 30-day audit logs.
High
CanisterSprawl + TeamPCP Supply Chain Worm — npm / PyPI / Docker Hub
Active supply chain campaign · 3 package registries
GitGuardian researchers identified three simultaneous supply chain campaigns hitting npm, PyPI, and Docker Hub over a 48-hour window. The CanisterSprawl and TeamPCP campaigns deploy worm-propagation logic that copies malicious payloads to other packages in the developer's local environment. Infected packages include typosquats of popular AI/ML utilities. The Docker Hub campaign injects a reverse shell into base images used in CI/CD pipelines.
Action: Audit all package installs from last 7 days, check Docker image integrity.
High
Qilin Ransomware — SEL Engineering Attack (April 20)
Threat Actor: Qilin (RaaS) · Target: Critical infrastructure / OT
Qilin ransomware group claimed responsibility for an attack on Schweitzer Engineering Laboratories (SEL) on April 20, 2026. SEL produces protection relays and automation systems used in power grids globally. The attack is significant because it targets OT-adjacent engineering assets, not just corporate IT. Qilin has been increasingly targeting critical infrastructure and defense-adjacent firms as a deliberate escalation strategy.
Action: Review OT/IT segmentation and backup integrity for engineering systems.
High
Salt Typhoon (PRC) — 200+ Organizations Compromised, Congressional Emails Accessed
Threat Actor: Salt Typhoon (APT41 affiliate) · Sector: Telecom, Government
PRC-linked Salt Typhoon remains active and expanding. TrendMicro confirmed the campaign has now breached 200+ organizations, including US public sector and telecom providers, with congressional staff email inboxes reportedly accessed. The group is maintaining long-term persistent access rather than destructive payloads — consistent with intelligence-collection objectives. The primary entry vector continues to be edge devices (routers, VPN appliances) with unpatched vulnerabilities.
Action: Emergency edge device patching + credential rotation + Salt Typhoon IoC hunt.
Critical
3.2 Billion Record Combo List — Plaintext Passwords + Phone Numbers
Scope: 3.2B records · Format: plaintext credentials · April 2026
A massive credential compilation of 3.2 billion records — including plaintext passwords and linked phone numbers — was circulated on dark web forums in April 2026. The dataset aggregates credentials from multiple prior breaches plus newly exfiltrated data. Phone numbers linked to accounts make this particularly dangerous for SIM-swap attacks and MFA bypass via SMS. The dump is indexed and searchable, making automated credential-stuffing attacks trivial.
Action: Force password resets, migrate off SMS MFA, enable credential stuffing detection.
Medium
Vercel Breach Widening — ShinyHunters Selling Data
Actor: ShinyHunters · Affected: Vercel, Context.ai customers
The Vercel breach first reported the week of April 17 has expanded in scope. ShinyHunters claim to have broader access than initially disclosed and are actively selling datasets on BreachForums. The breach is linked to the OAuth supply chain compromise via Context.ai, which allowed Lumma Stealer to extract session tokens from developer accounts. Developers using Vercel for deployment pipelines should assume environment variables and deployment tokens may be compromised.
Action: Rotate Vercel tokens, audit OAuth grants, review deployment logs.
Critical
Windsurf Zero-Click Prompt Injection RCE
CVE-2026-30615 · Tool: Windsurf AI IDE · No user interaction required
A zero-click prompt injection vulnerability in Windsurf allows an attacker to trigger remote code execution by embedding malicious instructions in a file or repository the developer opens. The AI assistant's context window processes the injected prompt and executes arbitrary shell commands without user confirmation. No proof-of-concept is publicly available, but the attack surface (any opened repository) is extremely broad.
Action: Update Windsurf immediately, disable autonomous shell execution if unpatched.
High
LMDeploy SSRF — Exploited 13 Hours After Disclosure
CVE-2026-33626 · CVSS 7.5 · Patched: LMDeploy 0.12.3
A server-side request forgery (SSRF) vulnerability in LMDeploy's API gateway was exploited in the wild just 13 hours after public disclosure — one of the fastest exploitation timelines observed in 2026. Attackers used the SSRF to reach AWS IMDSv1 metadata endpoints and exfiltrate instance credentials from self-hosted LLM deployments. Patch version 0.12.3 is available.
Action: pip install lmdeploy==0.12.3 + enforce IMDSv2 + rotate AWS credentials.
High
ssh-mcp Command Injection — No Patch Available
CVE-2026-7039 · CVSS 8.5 · No patch as of April 26
The ssh-mcp package — used to expose SSH capabilities to AI agents via MCP — has an unpatched command injection flaw (CVSS 8.5). Malicious tool inputs can break out of the intended SSH command context and execute arbitrary shell commands on the MCP host. No patch is available. The maintainer has been notified.
Action: Remove ssh-mcp from all MCP environments — no patch available.
Medium
Ollama Path Traversal — No Patch Available
CVE-2026-7020 · CVSS 6.3 · No patch as of April 26
A path traversal vulnerability in Ollama's model serving API allows an authenticated user to read arbitrary files on the server host. The flaw is in the model file loading endpoint where path normalization is insufficient. CVSS 6.3 — medium severity, but in enterprise deployments where Ollama serves multiple users or is behind an API gateway, the impact is elevated.
Action: Restrict Ollama to localhost only until patch is available.
-
01
Do Now
Patch Windows IKEv2 (CVE-2026-33824) + SharePoint (CVE-2026-32201)
Apply April 2026 Patch Tuesday updates. CISA deadline April 28 for SharePoint. Firewall-restrict IKE UDP 500/4500 if patching is delayed.
-
02
Do Now
Audit and secure all MCP servers — disable unauthenticated endpoints
Inventory all MCP servers, enforce auth on every endpoint, remove ssh-mcp, update Azure MCP, and rotate credentials. Anthropic will not patch at the protocol level.
-
03
Do Now
Force password resets + migrate from SMS MFA — 3.2B record credential dump
Run HaveIBeenPwned Enterprise check on your domain. Force resets on affected accounts. Move all accounts to TOTP/hardware key MFA. Credential stuffing attacks from this dump are already underway.
-
04
Today
Update LMDeploy to 0.12.3 + enforce AWS IMDSv2
pip install lmdeploy==0.12.3. Enforce IMDSv2 on all EC2 instances. Block 169.254.169.254 at host firewall. Rotate all AWS credentials accessible from affected hosts.
-
05
This Week
Update Windsurf, restrict to localhost, audit Salt Typhoon IoCs on edge devices
Update Windsurf to latest version. Patch edge network devices against Salt Typhoon entry vectors. Review CISA AA24-038A for specific detection guidance. Rotate edge device credentials.
// biggest risk this period
MCP protocol design flaw enables unauthenticated RCE across 7,000+ AI servers — Anthropic declined to patch.
The MCP ecosystem is the connective tissue of modern AI development tooling — Claude, Cursor, Windsurf, and hundreds of agent frameworks all rely on it. With 10 CVEs assigned, 7,000+ servers exposed, and 150M+ downloads, and with Anthropic declining to fix the underlying protocol, every AI-enabled development environment is now a potential attack surface. Remediation requires manual action by every individual server implementer — meaning most will remain vulnerable for months.