Critical Zero-Click Vulnerability Discovered in Claude Desktop Extensions, Anthropic Declines to Fix
Security researchers at LayerX have uncovered a severe zero-click vulnerability affecting Claude Desktop Extensions (DXT) that could allow attackers to execute malicious code remotely without any user interaction. The flaw, assigned a maximum CVSS severity score of 10.0, impacts approximately 50 Claude Desktop Extensions and potentially affects over 10,000 active users. The vulnerability exploits how Claude Desktop Extensions operate with full system privileges, unlike traditional browser extensions that run in sandboxed environments. According to LayerX's research, an attacker could craft a malicious Google Calendar event containing hidden instructions that Claude's AI would automatically execute when processing the event. This creates a dangerous attack vector where seemingly innocent calendar entries can trigger system-wide compromise. The root cause lies in Claude's Model Context Protocol (MCP) implementation, which allows the AI to autonomously chain together different tools and functions based on user prompts. When researchers instructed Claude to "check my latest events and take care of it," the AI interpreted vague instructions embedded in calendar events as legitimate commands to execute, demonstrating how the system lacks proper security boundaries between data sources and execution environments. Claude Desktop Extensions differ significantly from standard browser add-ons. While Chrome extensions are packaged as .crx files and operate within browser sandboxes, Claude DXT are distributed as .mcpb bundles through Anthropic's marketplace and execute with unrestricted system access. This architecture enables Claude extensions to read arbitrary files, execute system commands, access stored credentials, and modify operating system settings. When LayerX reported the vulnerability to Anthropic, the company declined to implement a fix, stating the issue "falls outside our current threat model." Anthropic characterized Claude Desktop's MCP integration as a local development tool designed for users who explicitly configure and grant permissions to MCP servers. The company emphasized that users should exercise caution when installing MCP servers, similar to installing any third-party software. However, LayerX's principal security researcher Roy Paz argues this response highlights a critical gap in AI security responsibility. The vulnerability demonstrates what he calls the "classic catch-22 of AI" - organizations need to grant AI tools deep system access to unlock productivity benefits, but AI providers often disclaim responsibility when security issues arise from that access. This incident underscores broader concerns about AI security as these systems become more integrated into enterprise environments. The ability for AI assistants to autonomously execute commands based on external data sources creates new attack surfaces that traditional security models may not adequately address. As AI tools gain more sophisticated capabilities and deeper system integration, the industry faces mounting pressure to develop comprehensive security frameworks that balance functionality with protection against emerging threats.
A critical security vulnerability has been discovered in Claude Desktop Extensions that allows attackers to execute malicious code on target systems without requiring any user interaction, according to new research from browser security firm LayerX. The zero-click exploit affects approximately 50 Claude Desktop Extensions and could impact more than 10,000 active users worldwide.
The vulnerability, disclosed in a February 9 report, demonstrates how attackers can leverage seemingly harmless Google Calendar events to achieve remote code execution on systems running vulnerable Claude Desktop Extensions. LayerX assigned the flaw a maximum severity rating of 10.0 on the Common Vulnerability Scoring System (CVSS), indicating the highest possible risk level.
Unlike traditional browser extensions that operate within sandboxed environments, Claude Desktop Extensions execute with full system privileges on host machines. This architectural difference creates significant security implications, as these extensions can perform sensitive operations including reading arbitrary files, executing system commands, accessing stored credentials, and modifying operating system configurations.
The attack vector exploits Claude's Model Context Protocol (MCP) implementation, which enables the AI assistant to autonomously combine different tools and functions based on user requests. LayerX researchers demonstrated the vulnerability by instructing Claude to "check my latest events and take care of it." The AI interpreted this vague prompt as authorization to execute arbitrary instructions embedded within calendar events, effectively treating external data as trusted commands.
Claude Desktop Extensions are distributed as .mcpb bundles through Anthropic's extension marketplace, containing MCP server implementation code and manifest files that define exposed functions. This packaging differs substantially from Chrome extensions (.crx files) that operate under strict browser security constraints. The unrestricted execution environment of Claude DXT creates opportunities for exploitation that don't exist with conventional browser add-ons.
When LayerX reported their findings to Anthropic, the company declined to implement remediation measures, stating the vulnerability "falls outside our current threat model." Anthropic characterized Claude Desktop's MCP integration as a local development tool designed for users who explicitly configure and grant permissions to MCP servers within their own environments.
An Anthropic spokesperson emphasized that the described scenario requires targeted users to intentionally install and grant permissions to run these tools without prompts. The company recommended that users exercise equivalent caution when installing MCP servers as they would with any third-party software installation.
Despite Anthropic's response, LayerX's principal security researcher Roy Paz maintains the maximum severity rating based on established vulnerability assessment frameworks from the Forum of Incident Response and Security Teams (FIRST). Paz highlighted what he termed the "classic catch-22 of AI" - organizations must provide AI tools with deep system access to realize productivity benefits, yet AI providers often disclaim responsibility for security consequences resulting from that access.
This incident illuminates broader challenges facing the AI industry as these systems become increasingly integrated into enterprise environments. The autonomous nature of AI assistants, combined with their ability to chain together multiple tools and data sources, creates novel attack surfaces that traditional security models may inadequately address.
The vulnerability also raises questions about responsibility and accountability in AI security. As AI tools gain more sophisticated capabilities and deeper system integration, the industry faces pressure to develop comprehensive security frameworks that balance functional capabilities with robust protection against emerging threats.
The LayerX research underscores the need for what Paz describes as an "AI shared responsibility model" that clearly delineates security obligations between AI providers, extension developers, and end users. Without such frameworks, organizations deploying AI tools may face unexpected security risks that fall outside traditional threat models.
As AI assistants become more prevalent in enterprise environments, security professionals must carefully evaluate the permissions and access levels granted to these systems. The Claude Desktop Extensions vulnerability serves as a cautionary example of how AI's autonomous decision-making capabilities can be exploited when proper security boundaries are not enforced.