Critical Zero-Click Vulnerability in Claude Chrome Extension Exposes Millions to Silent Attacks
A recently discovered zero-click vulnerability in Anthropic’s Claude Chrome Extension has exposed over 3 million users to potential silent prompt-injection attacks. This flaw allowed malicious websites to hijack the AI assistant without any user interaction, enabling attackers to steal Gmail access tokens, read Google Drive files, export chat history, and send emails—all without the user’s knowledge.
Understanding the Vulnerability
The exploit, identified by KOI security researchers, involved two primary flaws that, when combined, could lead to a full browser takeover:
1. Overly Permissive Origin Allowlist: The Claude extension’s messaging API accepted messages from any subdomain under `.claude.ai`. This broad wildcard allowed any subdomain to send messages to the extension, including potentially malicious ones.
2. Third-Party Component Flaw: Anthropic utilized Arkose Labs for CAPTCHA verification, with components hosted on `a-cdn.claude.ai`. Due to the permissive allowlist, these components had the same messaging permissions as the main `claude.ai` domain.
Researchers discovered that older versions of the Arkose CAPTCHA component, accessible through predictable URLs, contained a DOM-based Cross-Site Scripting (XSS) vulnerability. This flaw arose from two issues:
– The component accepted `postMessage` data from any parent origin without validating `event.origin`.
– It rendered a user-controlled `stringTable` field as raw HTML using React’s `dangerouslySetInnerHTML` without proper sanitization.
The Exploit Chain
An attacker could embed the vulnerable Arkose component within a hidden `
This injected script could then call `chrome.runtime.sendMessage()` targeting the Claude extension with any attacker-controlled prompt. Since the extension trusted the `.claude.ai` origin, it would pass the prompt through, and Claude would execute the instruction as if it were a legitimate user command.
The entire process occurred silently, without any clicks, permission dialogs, or visible indicators to the user. Given Claude’s capabilities as an autonomous browser agent—navigating pages, executing JavaScript, and interacting with web services—the attacker’s injected prompt carried the same trust level as legitimate user instructions.
Potential Impact
The implications of this vulnerability were severe. Demonstrated attack scenarios included:
– Stealing Persistent Google OAuth Access Tokens: Allowing attackers to maintain long-term access to a user’s Google services.
– Reading Gmail and Google Drive Contents: Providing unauthorized access to personal emails and files.
– Exfiltrating LLM Conversation History: Enabling attackers to access and extract sensitive conversations.
Response and Mitigation
The vulnerability was responsibly disclosed to Anthropic via HackerOne on December 26, 2025. Anthropic confirmed and triaged the issue within 24 hours and deployed a fix on January 15, 2026. The update replaced the wildcard allowlist with a strict origin check requiring exactly `https://claude.ai`.
The Arkose Labs XSS vulnerability was separately reported on February 3, 2026, confirmed within 24 hours, and fully patched by February 19, 2026. The vulnerable URL now returns a 403 response, preventing further exploitation.
Users are advised to verify that their installed version of the Claude Chrome Extension is 1.0.41 or higher by navigating to `chrome://extensions` in their browser.
Broader Implications
This incident highlights a systemic risk in AI browser agents: the security perimeter is only as strong as the weakest trusted origin. Third-party vendor components hosted on first-party subdomains can silently expand that trust boundary in ways that aren’t immediately obvious.
As AI assistants gain deeper browser access, attackers gain higher-value targets, and supply chain trust issues become more critical. It’s essential for developers to implement strict origin checks and regularly audit third-party components to prevent similar vulnerabilities.
Conclusion
The discovery and prompt mitigation of this zero-click vulnerability in the Claude Chrome Extension underscore the importance of vigilant security practices in the development and maintenance of browser extensions. Users should ensure their extensions are up-to-date and remain cautious of potential security risks associated with third-party components.