Combined Report April 26, 2026

Threat Intel Bi-Weekly + AI Vulnerability Monitor

Coverage: April 22–26, 2026  ·  4 areas: CVEs & Exploits, AI & Supply Chain, Threat Actors, Dark Web

14
Total Findings
4
Critical
7
High
8
AI CVEs
3
Medium
Coverage: April 22 – 26, 2026  ·  Sources: NVD, CISA KEV, Exploit-DB, Mandiant, CrowdStrike, HaveIBeenPwned, GitGuardian, The Hacker News, Cyfirma, TrendMicro, SentinelOne

CVEs & Exploits

3 findings
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.
Remediation
Apply the April 2026 Patch Tuesday update immediately. If patching is not immediately possible, restrict IKE/UDP 500 and 4500 traffic at the perimeter firewall to trusted peers only. Monitor for anomalous IKE negotiation traffic in SIEM.
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.
Remediation
On-premises SharePoint administrators must apply KB5002670 immediately. Verify patch installation via SharePoint Management Shell: Get-SPProduct -Local | Select DisplayName,PatchLevel. SharePoint Online: no action required.
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.
Remediation
Samsung MagicINFO: upgrade to 21.1050 or later. SimpleHelp: update to 5.3.9+ and restrict admin panel to trusted IPs. D-Link DIR-823X: apply vendor firmware update or replace end-of-life devices. All three have known PoC exploits in public circulation.
Action: Audit environment for Samsung MagicINFO, SimpleHelp RMM, and D-Link DIR-823X.

AI & Supply Chain

3 findings
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.
Remediation
Audit all MCP servers in your environment immediately. Require authentication on all MCP endpoints — do not expose MCP servers without auth. Review tool definitions for prompt injection patterns. Pin tool versions and validate tool schemas before execution. Disable any MCP servers not actively required. Monitor MCP GitHub Security Advisories for per-server patches.
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.
Remediation
Update azure-mcp to the patched version immediately (check Azure MCP releases for the latest). Rotate all Azure credentials that were accessible via the MCP server. Restrict Azure MCP server network access to localhost or trusted CI/CD runners only. Review Azure Activity Logs for unauthorized API calls in the 30 days prior to patching.
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.
Remediation
Run npm audit and pip audit across all projects. Check Docker image SHAs against official registry manifests. Remove any newly installed packages with unexpected postinstall scripts. Enable Sigstore/Cosign verification for Docker images. Block outbound connections from CI runners to unexpected destinations. Review GitGuardian IoC list for affected package names.
Action: Audit all package installs from last 7 days, check Docker image integrity.

Threat Actor Activity

2 findings
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.
Remediation
Segment OT/ICS environments from corporate IT. Enforce offline or air-gapped backups for engineering workstations. Review and rotate credentials for engineering software and file-sharing systems. Enable MFA on all remote access. Monitor for lateral movement from IT to OT segments using behavioral analytics. Review Qilin IoCs published by Cyfirma.
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.
Remediation
Patch all edge devices (routers, firewalls, VPN appliances) on emergency timelines. Rotate credentials for accounts with admin access to network edge. Hunt for persistent access: unusual SNMP traffic, unexpected BGP peering, living-off-the-land techniques on network devices. Review CISA advisory AA24-038A for Salt Typhoon-specific IoCs and detection rules.
Action: Emergency edge device patching + credential rotation + Salt Typhoon IoC hunt.

Dark Web & Credential Leaks

2 findings
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.
Remediation
Enforce mandatory password resets for all accounts where the email domain appears in breach databases. Check employee accounts via HaveIBeenPwned Enterprise. Migrate all accounts from SMS-based MFA to authenticator apps or hardware keys. Deploy credential-stuffing detection (rate limiting, impossible travel rules, device fingerprinting). Run a dark web monitoring sweep using your TPRM tooling.
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.
Remediation
Rotate all Vercel deployment tokens and environment variable secrets immediately. Audit Vercel project team member access logs. Check OAuth app authorizations for any Context.ai or unfamiliar apps — revoke all unauthorized grants. Review deployment logs for any unexpected deployments in the last 30 days. Enable Vercel audit logging if not already active.
Action: Rotate Vercel tokens, audit OAuth grants, review deployment logs.

AI Tool Vulnerability Monitor

4 CVEs
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.
Remediation
Update Windsurf to the latest version immediately (check Windsurf release notes for the patched build). Until patched, disable Windsurf's ability to execute shell commands autonomously. Do not open untrusted repositories in Windsurf. Review all commands executed by Windsurf in the past 30 days for anomalies.
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.
Remediation
Upgrade LMDeploy to 0.12.3: pip install lmdeploy==0.12.3. Enforce IMDSv2 on all AWS EC2 instances hosting LMDeploy — IMDSv1 is exploitable via SSRF. Block outbound requests from LMDeploy processes to instance metadata IP (169.254.169.254) at the host firewall level. Rotate any AWS credentials that were accessible from affected instances.
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.
Remediation
Remove or disable ssh-mcp immediately until a patch is released. If SSH-over-MCP capability is required, implement a custom server with strict input sanitization and command allowlisting. Monitor the NVD entry and package repository for patch release.
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.
Remediation
Restrict Ollama API access to trusted local users only (bind to localhost, not 0.0.0.0). Do not expose Ollama directly on the network without an authenticated proxy. Monitor the NVD entry for patch availability. Apply filesystem permissions to limit what the Ollama process can read.
Action: Restrict Ollama to localhost only until patch is available.

Priority Action Matrix

// 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.