Skip to content
Registry/APM-0087
APM-00874SEVEREReported February 25, 2026

Check Point found Claude Code flaws allowing code execution and Anthropic API key theft from a malicious repository

Agent Involved
Claude
Estimated Damage
Not quantified
Severity
4 / 5 Severe
Impact Band
Serious damage. Customer data affected, security incident, or financial losses $10k–$100k.

Independent project · aggregated from public reports and may be unverified — see the primary source below · not affiliated with or endorsed by any company or product named.

Check Point Research disclosed three critical vulnerabilities in Claude Code that exploit Hooks, MCP servers and environment variables through malicious repository configuration files to compromise developer machines and workspace data. CVE-2025-59536 was an MCP user-consent bypass: a bug in the startup trust dialog let Claude Code execute code contained in a project before the user accepted the dialog, triggered simply by starting Claude Code in an untrusted directory. CVE-2026-21852 let attackers trick Claude Code into issuing API requests to an attacker-controlled server, exposing the user's Anthropic API key. Reports ran from July to October 2025, fixes shipped in August, September and December 2025, and Check Point disclosed publicly on 25 February 2026.

Verified Facts

  • Three vulnerabilities spanned Hooks, MCP servers and environment variables in Claude Code
  • CVE-2025-59536 let project code execute before the user accepted the trust dialog
  • CVE-2026-21852 exposed the user's Anthropic API key to an attacker-controlled server

Not Publicly Confirmed

  • Whether any of the flaws were exploited in the wild
  • CVSS scores were not stated in the writeup

Operational Lessons

  • A trust dialog is worthless if code paths execute before the user answers it
  • Opening an untrusted repository in an agentic CLI is equivalent to running its code
Caught in the Hook: RCE and API Token Exfiltration Through Claude Code Project Files (Check Point Research)research.checkpoint.com
Case No.
APM-0087
Reported
February 25, 2026
Attribution
Anonymous
Discussion

More Cases

0
May 7, 2026

Prompt injection reached host-level code execution in Microsoft Semantic Kernel through eval() and a stray annotation

Microsoft disclosed two vulnerabilities that turn prompt injection into host compromise in its Semantic Kernel agent framework, which has over 27,000 GitHub stars. CVE-2026-26030 affects the Python package before 1.39.4: the default in-memory vector store filter is a Python lambda executed with eval() on unsanitized model-controlled input, so an attacker could escape the template string, traverse Python's class hierarchy, bypass the AST blocklist validator and run arbitrary commands, demonstrated by launching calc.exe from a single prompt injection. CVE-2026-25592 affects the .NET SDK before 1.71.0: DownloadFileAsync was accidentally marked with a [KernelFunction] attribute, exposing it to the model with an entirely AI-controlled, unvalidated local file path, allowing writes to locations such as the Windows Startup folder and thus sandbox escape.

0
APM-0080Microsoft 365 Copilot4SEVERE
Jun 15, 2026

SearchLeak let a single click on a malicious link pull emails, files and MFA codes out of Microsoft 365 Copilot

Varonis Threat Labs disclosed CVE-2026-42824, a critical flaw in Microsoft 365 Copilot Enterprise Search. Clicking a single crafted link chained three bugs: injection of the URL parameter into the prompt, a rendering race condition, and abuse of Content Security Policy allowlisting to exfiltrate data through Bing's infrastructure. The attack could reach emails and calendar details, indexed SharePoint and OneDrive files, one-time and MFA codes, password-reset links, meeting notes and salary data. Because Copilot Enterprise is a managed service, tenant admins could not patch it themselves; Microsoft mitigated the flaw on its backend.

0
APM-0083Cursor3MODERATE
Jan 14, 2026

Cursor's command allowlist could be bypassed with shell built-ins, giving prompt injection a silent path to code execution

Pillar Security disclosed CVE-2026-22708 in Cursor. In Auto-Run Mode with an allowlist enabled, shell built-ins such as export, typeset, declare, readonly, unset and local were implicitly trusted by Cursor's server-side evaluator and executed without appearing in the allowlist or requiring approval, because they run inside the shell session rather than as separate binaries. An attacker delivering indirect prompt injection could silently poison environment variables and then trigger malicious code through trusted developer tools, producing both zero-click and one-click remote code execution. Pillar reported it in August 2025, Cursor acknowledged it as a systemic issue in September 2025, and the fix shipped in version 2.3 in January 2026, which now requires explicit approval for any command the parser cannot classify.