Coverage: May 3 – May 5, 2026  ·  Sources: NVD, CISA KEV, Socket.dev, Wiz, The Register, The Hacker News, Microsoft Security Blog, CERT-EU, Sysdig, Cybersecurity Dive, CyberScoop, Mandiant M-Trends 2026, CM Alliance, HawkEye
Threat Intel May 5, 2026

Threat Intel Bi-Weekly

Coverage: May 3–5, 2026  ·  5 areas monitored  ·  NVD, CISA KEV, Threat Actor Intel, Dark Web, AI Security

12 Total Findings
3 Critical
6 High
3 AI CVEs
3 Medium
01

CVEs & Exploits

NVD · CISA KEV · Exploit-DB · Vendor Bulletins
HIGH CVE-2026-31431 Copy Fail — CISA KEV Added May 3, FCEB Patch Deadline May 15

Linux kernel local privilege escalation now on CISA's Known Exploited Vulnerabilities catalog after active exploitation confirmed in the wild. The Copy Fail vulnerability (CVSS 7.8) affects all Linux distributions running kernels built since 2017. An unprivileged local user executes a 732-byte Python script to perform a controlled 4-byte overwrite of the kernel page cache, corrupting setuid binaries and escalating to root. Container escape vector: shared page cache across containers means an unprivileged container process can corrupt a host setuid binary. Federal Civilian Executive Branch agencies must patch by May 15, 2026.

REMEDIATION Apply kernel patches immediately: Ubuntu/Debian: apt update && apt upgrade linux-image-generic. RHEL/Amazon Linux: dnf update kernel. Patched kernel versions: 6.18.22, 6.19.12, 7.0. Upstream fix: mainline commit a664bf3d603d. If patching not immediate: disable AF_ALG via seccomp policy (SCMP_ACT_ERRNO for AF_ALG socket calls) on all containers and Kubernetes pods. Block unprivileged user namespace creation where not needed: echo 0 > /proc/sys/kernel/unprivileged_userns_clone
► Patch all Linux systems immediately — FCEB deadline May 15. Apply seccomp AF_ALG block to all containers as immediate mitigation.
HIGH CVE-2024-1708 — ConnectWise ScreenConnect Added to CISA KEV, Federal Deadline May 12

ConnectWise ScreenConnect path traversal vulnerability (CVSS 8.4) added to CISA KEV on April 29. The flaw allows an authenticated attacker to traverse directories outside the intended scope. Federal agencies have until May 12 to patch. ScreenConnect is widely deployed for remote IT support and managed service provider access — a compromised instance provides persistent access to all endpoints the tool manages. Often chained with CVE-2024-1709 (authentication bypass, CVSS 10.0) for unauthenticated full takeover.

REMEDIATION Upgrade ConnectWise ScreenConnect to version 23.9.8 or later immediately. Versions prior to 23.9.8 are affected. Run the ConnectWise Update Wizard or download from the ConnectWise partner portal. Verify patched version is deployed before the May 12 FCEB deadline. If upgrade is not immediately possible: take the ScreenConnect instance offline, restrict access to trusted IPs only, and enable MFA for all administrator accounts. Audit recent session logs for unauthorized connections.
► Patch ScreenConnect to 23.9.8+ before May 12 FCEB deadline. Audit all recent remote sessions for unauthorized access.
MEDIUM CVE-2026-32202 — Windows Shell LNK Spoofing Actively Exploited, Russian Campaign Confirmed

Microsoft confirmed active exploitation of CVE-2026-32202 (CVSS 4.3), a Windows Shell protection mechanism failure enabling spoofing attacks via malicious LNK shortcut files. Exploitation linked to a Russian-linked campaign targeting Ukraine and European organizations. Weaponized LNK files trigger NTLM credential hash leakage via UNC path SMB connections — hashes usable for relay attacks or offline cracking. Represents an incomplete patch bypass of CVE-2026-21510. CISA KEV-listed with federal patch deadline May 12.

REMEDIATION Apply Microsoft April 2026 Patch Tuesday updates immediately. Disable NTLM authentication where feasible (modern environments): configure security policy to restrict outgoing NTLM traffic. Block outbound SMB (TCP 445) to external/untrusted destinations at the network perimeter. Enable Protected Users security group for privileged accounts. Audit email and browser downloads for LNK files from untrusted sources. Enforce Mark of the Web (MOTW) policies.
► Apply April 2026 Patch Tuesday immediately. Block outbound SMB to external IPs at firewall. Audit for LNK file delivery in recent email/download logs.
MEDIUM CVE-2026-40542 — Apache HttpClient SCRAM-SHA-256 Authentication Bypass (High)

High-severity authentication bypass in Apache HttpClient affecting SCRAM-SHA-256 mutual authentication. A missing critical step in the SCRAM-SHA-256 handshake allows an attacker to manipulate the authentication flow, causing the client to incorrectly accept server authentication without verification. This enables establishment of unauthorized trusted sessions with servers using SCRAM-SHA-256 — a protocol deployed for secure credential exchange in database connections (MongoDB, PostgreSQL via SASL), messaging systems, and enterprise middleware. CVSS score: High.

REMEDIATION Upgrade Apache HttpClient to the latest patched version (check https://hc.apache.org/httpcomponents-client-5.x/ for current release). Review all application code that uses HttpClient with SCRAM-SHA-256 authentication. If upgrade is not immediate: avoid using HttpClient for SCRAM-SHA-256 authenticated connections to untrusted servers; consider server certificate pinning as additional defense.
► Upgrade Apache HttpClient immediately. Audit applications using SCRAM-SHA-256 via HttpClient.
02

AI & Supply Chain

PyPI · npm · GitHub Advisories · AI Tool CVEs
CRITICAL TeamPCP Mini Shai-Hulud — SAP npm + Intercom + Lightning PyPI Supply Chain, Self-Propagating AI Config Abuse

TeamPCP's fourth supply chain wave poisoned official SAP npm packages (mbt@1.2.48, @cap-js/db-service@2.10.1, @cap-js/postgres@2.2.2, @cap-js/sqlite@2.2.2), Intercom npm packages (7.0.4, 7.0.5), and PyPI lightning (2.6.2, 2.6.3) on April 29-30. Preinstall hooks bootstrap a Bun runtime and execute a credential stealer that harvests GitHub/npm tokens, AWS/Azure/GCP/K8s secrets, and browser passwords, encrypting exfiltration with RSA-4096 + AES-256-GCM to attacker-controlled GitHub repos named with Dune-themed patterns. Critically: the payload self-propagates by writing malicious .claude/settings.json (abusing Claude Code SessionStart hook) and .vscode/tasks.json (VS Code auto-run) to all accessible repos, poisoning every package the victim maintains via their stolen npm token. First supply chain attack to weaponize AI coding agent configuration files as a persistence vector.

REMEDIATION Remove poisoned versions immediately. Safe versions: @cap-js/sqlite v2.4.0 or v2.3.0, @cap-js/postgres v2.3.0, @cap-js/hana v2.8.0 or v2.7.2, @cap-js/db-service v2.10.1 (re-released clean), mbt v1.2.49. Intercom: avoid 7.0.4, 7.0.5; use latest clean version. PyPI lightning: avoid 2.6.2 and 2.6.3; use 2.6.1 or latest clean release. Run npm audit and pip audit. Rotate ALL GitHub tokens, npm tokens, and cloud credentials if affected versions were installed in any environment. Audit all repos for injected .claude/settings.json and .vscode/tasks.json files. Review GitHub Actions logs for unexpected workflows or new repositories matching <word>-<word>-<3digits> naming pattern.
► Remove poisoned package versions. Rotate all tokens and cloud credentials. Audit repos for injected .claude/settings.json and .vscode/tasks.json files immediately.
CRITICAL Comment and Control — Cross-Agent Prompt Injection (CVSS 9.4), Claude Code / Gemini CLI / Copilot Agent

A single prompt injection pattern confirmed against three major AI coding agents simultaneously: Anthropic Claude Code Security Review (PR title injection extracted ANTHROPIC_API_KEY and GITHUB_TOKEN), Google Gemini CLI Action (issue comment injection leaked GEMINI_API_KEY publicly), and GitHub Copilot Agent (HTML comment payload bypassed all three GitHub runtime defense layers to exfiltrate GITHUB_TOKEN and COPILOT_API_TOKEN). Rated CVSS 9.4 Critical. No CVE issued by any vendor. GitHub classified the issue as a known architectural limitation. Attacks fire automatically from GitHub Actions workflows — no victim action required for Claude Code or Gemini. Any AI agent that ingests untrusted GitHub data and has access to execution tools in the same runtime is potentially affected.

REMEDIATION Claude Code Security Review: Update to latest version and restrict agent scope to trusted first-party inputs only in workflow YAML — do not enable processing of untrusted external PRs. Gemini CLI Action: Update to latest version (Google added guardrail prompts; underlying trust model gap remains). GitHub Copilot Agent: Restrict GITHUB_TOKEN to minimum required scopes, enforce CODEOWNERS on sensitive files, do not assign untrusted external issues to Copilot. All three: apply least-privilege tool access, enable secret scanning on agent outputs, monitor GitHub Actions logs for anomalous tool invocations or unexpected outbound requests.
► Restrict AI agent CI/CD pipelines to trusted-only inputs. Apply least-privilege token scopes. Audit recent GitHub Actions runs for credential leak indicators.
HIGH Gemini CLI CVSS 10.0 — Zero-Trust CI/CD RCE, Patch Available

Maximum-severity (CVSS 10.0) RCE in Google Gemini CLI all versions prior to 0.39.1 and run-gemini-cli GitHub Action prior to v0.1.22. In headless and CI mode, Gemini CLI automatically trusted any workspace .gemini/ configuration without review or sandboxing. A malicious pull request planting a .gemini/ config executes on the CI host before any sandbox initializes. The --yolo flag bypassed tool allowlists entirely. Impact: CI/CD secrets theft, supply-chain pivot, lateral movement through GitHub Actions environment variables.

REMEDIATION Upgrade: npm install -g @google/gemini-cli@0.39.1 (or 0.40.0-preview.3). Update run-gemini-cli GitHub Action to v0.1.22 in all workflow YAML files. Audit all CI/CD pipelines that used Gemini CLI in headless mode. Review all repository .gemini/ directories for malicious configuration files. Revoke and rotate any GitHub secrets or tokens accessible from affected workflows. Never use --yolo flag in any production or CI/CD context.
► Upgrade Gemini CLI to 0.39.1+ and Action to v0.1.22 immediately. Audit .gemini/ directories in all repos.
03

Threat Actors & Dark Web

Mandiant · CrowdStrike · CyberScoop · CM Alliance
HIGH M-Trends 2026 — Mean Time-to-Exploit Now -7 Days, 28.3% of CVEs Exploited Within 24h of Disclosure

Mandiant's M-Trends 2026 report (based on 500,000+ hours of incident response in 2025) confirms the exploit window has inverted: mean time-to-exploit is now negative 7 days — exploitation is routinely underway before patches exist. 28.3% of CVEs are exploited within 24 hours of public disclosure, compared to a 44-day average in 2025 and 700+ days in 2020. AI-assisted attacks rose 89% year-over-year per CrowdStrike. Exploitation remains the leading initial access vector for the sixth consecutive year (32% of intrusions). QUIETVAULT, a newly documented credential stealer, specifically checks compromised machines for local AI CLI tools and executes predefined prompts to exfiltrate AI tool configurations. Attackers can now transfer access between criminal actors in under 30 seconds.

REMEDIATION Adopt continuous vulnerability prioritization — traditional scan-and-patch cycles are structurally inadequate when mean time-to-exploit is negative. Deploy runtime detection (EDR/XDR) on all internet-facing systems. Enable CISA KEV as a real-time patch priority signal. Implement network-based detection for early exploit indicators on internet-exposed services. Audit local AI CLI tools (Claude Code, Gemini CLI, Codex CLI, Cursor) for QUIETVAULT-style reconnaissance — check for unexpected config file reads or exfiltration patterns.
► Shift to continuous exploit-signal-based patching. Treat CISA KEV additions as immediate-patch triggers. Audit AI CLI tool configs for unauthorized reads.
HIGH Salt Typhoon — Confirmed Still Active Across 80+ Countries, Telecom and Government Networks

FBI leadership confirmed in February 2026 that Salt Typhoon, the PRC-linked APT responsible for the 2024 U.S. telecom infrastructure breach, remains 'still very much ongoing.' Intrusions have impacted telecommunications providers and government bodies in 80+ countries. The threat actor pairs broad network access with indiscriminate collection, targeting edge devices that lack EDR telemetry. AT&T and Verizon reportedly blocked release of Salt Typhoon security assessment reports. Congressional email systems confirmed compromised. Related group UAT-7290 is simultaneously targeting U.S. and allied telecom providers via edge device exploits. Salt Typhoon's primary access method is exploitation of vulnerable legacy edge devices — not zero-day exploits.

REMEDIATION Audit and patch all internet-facing edge devices — VPNs, routers, firewalls — especially Fortinet, Cisco, and VMware appliances. Implement network traffic monitoring for unusual data flows to/from telecom infrastructure. Enable logging on all edge network devices including packet capture capability for sensitive segments. Deploy MFA on all remote access systems. Review CDR (Call Detail Records) access logs if applicable. Follow CISA/NSA Salt Typhoon mitigation guidance published December 2025.
► Patch all edge network devices immediately. Enable full logging on internet-facing infrastructure. Review CISA Salt Typhoon mitigation guidance.
HIGH April 2026 Breach Roundup — Booking.com, McGrawHill, Medtronic, EU Commission, LA City Attorney

April 2026 confirmed major breaches across enterprise, government, and healthcare sectors. Booking.com, McGrawHill, and Medtronic all confirmed unauthorized access incidents. The EU Commission experienced an infrastructure breach. The Los Angeles City Attorney's Office confirmed data exfiltration. Chinese Supercomputer research network, Eurail B.V., Basic-Fit fitness chain, Chipsoft healthcare IT, and the Los Angeles City Attorney's Office further demonstrate targeting across public sector, healthcare, travel platforms, and critical technology. Attack patterns include exploiting exposed APIs, credential theft via phishing, and supply chain compromise. Organizations with Chipsoft medical software (Netherlands-based, used across European hospitals) should audit for unauthorized access.

REMEDIATION Review breach notifications from any of the listed organizations for personal data exposure. Enterprise customers: contact affected vendors for scope assessments. Enable breach monitoring services (HaveIBeenPwned, identity protection). Reset passwords for any accounts associated with affected platforms. Enable MFA on all accounts. Monitor for credential stuffing activity on your own platforms. Healthcare organizations using Chipsoft software: contact vendor for security assessment and audit patient data access logs.
► Check HaveIBeenPwned for associated email addresses. Reset passwords and enable MFA for accounts with any of the affected services.
MEDIUM TeamPCP Exfil Infrastructure — 1,100+ GitHub Repos Created Under Dune-Themed Naming Pattern

Socket and Wiz forensics of the Mini Shai-Hulud campaign identified over 1,100 GitHub repositories created by compromised developer accounts, using the naming pattern <word>-<word>-<3 digits> (e.g., prescient-lasgun-242). These repositories serve as encrypted credential exfiltration drop points, with AES-256-GCM encrypted payloads. The same RSA public key used in the Bitwarden CLI and Checkmarx incidents confirms this is the fourth major TeamPCP wave. CI/CD secrets extracted directly from runner memory by reading /proc/<pid>/mem, bypassing GitHub Actions log masking entirely.

REMEDIATION Search your GitHub organization's repositories and any personal accounts used in development for repos matching <word>-<word>-<3digits> naming created in late April to early May 2026. Delete any such repositories if found. Audit GitHub Actions logs for unexpected outbound HTTP requests or unusual binary executions. Rotate all GitHub tokens and npm tokens that were active during late April. Add branch protection rules requiring PR review before publishing to npm. Monitor for unexpected npm package publications from your account.
► Search GitHub org for <word>-<word>-<3digits> repos. Rotate GitHub tokens. Audit npm publish logs for unauthorized releases.
04

AI Vulnerability Monitor

NVD · Veracode · Cycode · OWASP LLM Top 10 · AI Tool CVEs
CRITICAL NO-CVE-CommentAndControl — Anthropic Claude Code Security Review (GitHub Action), Google Gemini CLI Action,...

A cross-vendor prompt injection attack class named Comment and Control allows attackers to hijack AI agents running in GitHub Actions by embedding malicious instructions in PR titles, issue comments, or HTML comments. Confirmed against three agents: Anthropic Claude Code Security Review (PR title injection extracted ANTHROPIC_API_KEY and GITHUB_TOKEN), Google Gemini CLI Action (issue comment injection leaked GEMINI_API_KEY publicly), and GitHub Copilot Agent (HTML comment bypass defeated all three GitHub runtime defense layers to leak GITHUB_TOKEN and COPILOT_API_TOKEN). Rated CVSS 9.4 Critical by Anthropic. No CVE issued by any vendor. GitHub classified the issue as a known architectural limitation. The attack requires no external infrastructure and fires automatically from GitHub Actions workflows without victim action (except Copilot, which requires manual issue assignment). Affects any AI agent that ingests untrusted GitHub data and has access to execution tools and secrets in the same runtime.

REMEDIATION For claude-code-action: update to latest version and add input sanitization in workflow YAML — restrict the agent to trusted first-party inputs only; do not enable processing of untrusted external PRs without explicit scope restriction. For Gemini CLI Action: update to latest version (Google added guardrail prompts); note this does not eliminate the underlying trust model gap. For Copilot Agent: GitHub considers this a known architectural limitation — restrict GITHUB_TOKEN scope to minimum required, use CODEOWNERS rules, and do not assign untrusted external issues to Copilot. For all three: apply least-privilege tool access (only the tools needed for the specific task), implement secret scanning on agent outputs, and monitor GitHub Actions logs for anomalous tool invocations or unexpected outbound requests.
CRITICAL NO-CVE-GeminiCLI-CVSS10 — Google Gemini CLI (all versions prior to 0.39.1) and run-gemini-cli GitHub Actio...

Maximum-severity (CVSS 10.0) RCE in Google Gemini CLI and its run-gemini-cli GitHub Action. In headless and CI mode, Gemini CLI automatically trusted any workspace folder for loading .gemini/ configuration files without user review, sandboxing, or approval. An attacker with the ability to place content in a repository workspace via pull request could plant a malicious .gemini/ config file that the agent silently executed on the CI host before any sandbox initialized. The --yolo flag also bypassed tool allowlists entirely. Impact includes CI/CD secrets theft, supply-chain pivot, and lateral movement via GitHub Actions environment variables. CVE not yet formally assigned.

REMEDIATION Upgrade immediately: npm install -g @google/gemini-cli@0.39.1 or 0.40.0-preview.3. Update run-gemini-cli GitHub Action to v0.1.22 in all workflow YAML files. Audit all CI/CD pipelines that used Gemini CLI in headless mode. Review all repository .gemini/ directories for malicious configuration files. Revoke and rotate any GitHub secrets or tokens accessible from affected workflows. Do not use the --yolo flag in any production or CI/CD context.
CRITICAL NO-CVE-MCPSDKDesignFlaw — Anthropic MCP SDK (all versions), LangChain, LangFlow, Flowise (CVE-2026-40933),...

OX Security disclosed a systemic architectural weakness in Anthropic MCP SDK enabling arbitrary command execution across any MCP implementation. Attack paths include unauthenticated command injection via MCP STDIO, zero-click prompt injection leading to STDIO config rewrite, and MCP marketplace supply-chain attacks. Ten CVEs assigned across popular frameworks. Anthropic declined to change the protocol architecture. 7,000+ public MCP servers affected. Flowise patched as CVE-2026-40933; other frameworks have varying remediation status.

REMEDIATION Block public IP access to all MCP server ports immediately. Run MCP-enabled services inside dedicated sandboxes with no production credential access. Treat all external MCP configuration input as untrusted. Only install MCP servers from verified, audited sources. Monitor and log all MCP tool invocations. For Flowise: update to latest patched version (CVE-2026-40933 is patched). Disable STDIO transport for all public-facing deployments. Pin MCP server versions and verify integrity before deployment.
05

AI & Cybersecurity News

Krebs · The Hacker News · Dark Reading · Wired · Mandiant
INFO M-Trends 2026: AI-Assisted Attacks Up 89% YoY, Exploit Window Inverted — The Hacker News

Published May 4, 2026. Mandiant's M-Trends 2026 findings confirm AI has inverted the exploit timeline: mean time-to-exploit is -7 days, 28.3% of CVEs weaponized within 24 hours of disclosure. AI-assisted attacks rose 89% year-over-year per CrowdStrike data. QUIETVAULT credential stealer found targeting local AI CLI tool configurations. Ransomware access handoffs now occur in under 30 seconds. The report frames this as a structural failure of traditional patch management — defenders must shift to runtime detection and continuous risk signals.

REMEDIATION Read the full M-Trends 2026 report for board-level framing of the exploit timeline collapse. Implement CISA KEV as a real-time patching trigger. Deploy EDR on all internet-facing hosts. Conduct tabletop exercises around sub-24-hour patch scenarios.
► Share M-Trends 2026 findings with security leadership and update patch SLA policies to reflect the -7 day mean time-to-exploit reality.
INFO TeamPCP Weaponizes AI Agent Configs as Persistence Vector — First Documented Case

The Mini Shai-Hulud campaign marks the first publicly documented supply chain attack to weaponize AI coding agent configuration files (.claude/settings.json SessionStart hook, .vscode/tasks.json folderOpen trigger) as a persistence and propagation mechanism. The attack demonstrates that AI tool configuration files in repositories are now an active attack surface — any developer who opens a compromised repo in Claude Code or VS Code automatically executes the attacker's payload. This represents a qualitative evolution from prior supply chain attacks that relied on package installation hooks.

REMEDIATION Add .claude/settings.json and .vscode/tasks.json to your supply chain audit checklist. Implement pre-commit hooks that flag modifications to these files. Require PR review for all changes to AI agent configuration files. Configure Claude Code to require explicit user confirmation before executing SessionStart hooks in unfamiliar repositories. Educate developers: never open repositories from untrusted sources in AI coding agents without first reviewing all configuration files.
► Audit all repos for unexpected .claude/settings.json and .vscode/tasks.json changes. Add these files to supply chain monitoring and code review requirements.
Priority Action Matrix — May 5, 2026
01
DO NOW
Remove poisoned npm/PyPI packages immediately. Safe: @cap-js/sqlite v2.3.0+, mbt v1.2.49, Intercom use latest. Rotate ALL GitHub tokens, npm tokens, cloud credentials. Search GitHub org for repos matching <word>-<word>-<3digits> naming.
02
DO NOW
Patch Linux kernel Copy Fail (CVE-2026-31431): apt upgrade linux-image-generic or dnf update kernel. Block AF_ALG on containers via seccomp. FCEB deadline May 15.
03
TODAY
Patch ConnectWise ScreenConnect to 23.9.8+ (CISA KEV, federal deadline May 12). Upgrade Gemini CLI: npm install -g @google/gemini-cli@0.39.1. Update run-gemini-cli GitHub Action to v0.1.22.
04
TODAY
Restrict Claude Code, Gemini CLI, and Copilot Agent GitHub Actions to trusted first-party inputs only. Audit all repos for injected .claude/settings.json and .vscode/tasks.json files.
05
THIS WEEK
Apply April 2026 Patch Tuesday (CVE-2026-32202 Windows Shell, KEV). Upgrade Apache HttpClient (CVE-2026-40542). Implement CISA KEV as real-time patching trigger. Audit all AI CLI tool configs for QUIETVAULT-style reconnaissance.
Biggest Risk This Period
TeamPCP Mini Shai-Hulud supply chain campaign actively poisoned SAP, Intercom, and Lightning packages with self-propagating credential stealers that abuse AI coding agent configs (.claude/settings.json, .vscode/tasks.json) to persist and spread across every repo and CI/CD pipeline a developer touches.