A Bug in the Claude for Chrome Extension Has Survived Eight Fixes and Still Leaks Your Gmail
A flaw nicknamed 'ClaudeBleed' lets other browser extensions quietly read your email and calendar. After eight attempted patches, it apparently still works.
Key points
- A security flaw in the Claude for Chrome browser extension has resisted at least eight separate attempted fixes.
- The bug, nicknamed 'ClaudeBleed', can allow other extensions installed in the same browser to read a user's Gmail messages and Google Calendar events.
- Anyone who has the Claude extension installed alongside other Chrome extensions is potentially exposed.
- SecurityWeek first reported the persistence of the flaw across multiple patch attempts.
Anthropic's Claude for Chrome extension, a browser add-on that brings the Claude AI assistant directly into your browser, has a problem its makers haven't managed to close.
The flaw goes by the nickname 'ClaudeBleed'. It creates a gap that lets other extensions running in the same browser quietly reach into Claude's memory and pull out data it has handled, including content from Gmail and Google Calendar.
The failure mode is straightforward: the extension doesn't properly wall off the information it holds from other extensions. Browser extensions are supposed to be isolated from one another. This one isn't.
Should ordinary users be worried?
Yes, in a limited but real way. You're at risk if you have the Claude for Chrome extension installed alongside other extensions, especially ones from unfamiliar developers or sources outside the official Chrome Web Store.
A random website can't trigger this. But a malicious extension, perhaps a free PDF converter or coupon-finder that quietly misbehaves, could sit in your browser and use this flaw to read emails you've opened while Claude was active. Extension isolation was treated as a browser problem rather than an application problem. It's both.
This fits a pattern we've been tracking. On 13 July 2026 we reported how a dormant tracker sat inside ModHeader's official store version with 1.6 million users; the week before, ToddyCat's Umbrij malware was pulling Gmail directly from Google's API. The browser extension stack is quietly becoming one of the more reliable paths to your inbox.
Eight patches have come and gone. That's not a rounding error, it's a design problem that wasn't fully understood before code shipped.
What should you do right now?
Disable or remove the Claude for Chrome extension until a confirmed fix lands. Then open your browser's extension list and remove anything you don't recognise or actively use. Fewer extensions means a smaller attack surface, the kind of advice that's obvious and almost never followed.
Watch your Google account for unfamiliar activity. If you handle sensitive information regularly, Google's Advanced Protection Program is worth enabling.
One thing the eventual post-mortem will likely show: nobody audits browser extensions the way they audit software on a server. In 2026, the access levels are comparable. They deserve the same scrutiny.
