One Extension Can Hijack AI Assistants in Five Browsers

One Extension Can Hijack AI Assistants in Five Browsers

Forever Security found one browser extension can take over built-in AI helpers in Chrome, Edge, Comet, Opera Neon and Claude, reading files and using the camera…

Security researchers at Forever Security have demonstrated that one ordinary browser extension can hijack the built-in AI assistants in five Chromium-based products: Gemini Live in Chrome, Perplexity Comet, Microsoft Edge, Opera Neon and the Claude in Chrome extension. Once the extension was installed, the researchers say it could access each product's built-in AI with a single click. On Comet, Edge, Opera Neon and Claude in Chrome, it could drive the AI agent to act on behalf of an attacker. On Chrome and Comet, it could read files from the user's computer, and on Chrome it could also switch on the camera and microphone. The findings are researcher demonstrations, not attacks seen in the wild, and each requires the attacker's extension to be already running in the victim's browser.

All five products work on the same basic model, according to Forever Security. The AI has a 'body' inside the browser that can see the screen, open files, use the camera and take actions, and a separate 'brain' that runs on the company's servers and tells the body what to do. The body is designed to take orders from only one trusted web page, such as gemini.google.com for Chrome or perplexity.ai for Comet. A browser extension is not supposed to command that body, because an extension can change web pages but cannot control the browser itself. Forever Security's method was to seize the trusted page the body listens to and, through it, send the body its own commands. The extension needed only two common permissions: one that changes web pages, which ad blockers use, and one called declarativeNetRequest that changes how the browser sends and receives network traffic. Together they let the extension slip its own code into the trusted page and speak to the AI as if it were the vendor.

The Chrome case is not new. Forever Security researcher Gal Weizman first detailed it publicly in March as GlicJack, and Google fixed it in early January 2026 in Chrome version 143.0.7499.192. It is tracked as CVE-2026-0628 and rated 8.8 out of 10 by the U.S. cybersecurity agency CISA, which set the score because the National Institute of Standards and Technology has not. The other four findings are what Weizman added this year. Using the same idea, Forever Security said it reached the built-in AI in Comet, Edge, Opera Neon and Claude in Chrome. Only the Edge finding received a CVE, CVE-2026-55945, a lower-severity issue rated 4.2 that Microsoft fixed in Edge version 150.0.4078.48 on July 2. The Comet, Opera Neon and Claude findings have no CVE and rest on Forever Security's own account. The company said it earned about $20,000 in bug bounties across the five products, though its per-product figures add up to $20,500.

Forever Security listed what each attack could do. Comet was the worst case, the researchers said. Perplexity built Comet as a fully AI-driven browser, so its agent had broad powers: once hijacked, it could read any file on the computer, list the sites the user had visited, take screenshots, and act as the user. Perplexity had blocked extensions from its main page, so Forever Security used a leftover test address, testing.perplexity.com, that was not locked down the same way. Claude in Chrome was the mildest case. 'Claude in Chrome is a browser extension, not a browser,' the company wrote, and it called the finding the least serious because one extension was abusing another rather than an extension abusing a browser. Anthropic rated it medium severity and paid a bounty. Forever Security also said Anthropic named it the first to report the Claude finding, while earlier public reports from LayerX (ClaudeBleed, April) and Manifold Security (July) described similar gaps in later versions. Edge was the hardest to break. Microsoft had tried to block the extension trick, so Forever Security combined two weaknesses: it took over a Microsoft marketing page that was allowed to send prompts to the Edge AI, then used a race condition to switch the agent between its 'think' and 'act' modes at the right moment, causing it to carry out a prompt. Opera Neon was the easiest. Its AI took orders from opera.com, and Opera had not stopped extensions from running code on that page, so an extension could send commands straight through. Forever Security said Opera reported finding the same flaw on its own at around the same time but paid a reward anyway.

As of September 16, 2026, neither CVE was listed on the U.S. Known Exploited Vulnerabilities catalog, and no public evidence showed any of the five methods being used in a real attack. Every one of them assumes the attacker has already got the user to install the extension, the same starting point as many other browser attacks. For the two products with a CVE, the fix is to update Chrome to version 143.0.7499.192 or later and Edge to version 150.0.4078.48 or later. For Comet, Opera Neon and Claude in Chrome, Forever Security said each vendor paid a reward but did not give a date for fixing the exact method it described. Users of those three should make sure their software is up to date and review the extensions they have installed.

The common thread, Forever Security said, is that putting an AI agent inside the browser reopens a path that browsers work hard to close, allowing a low-privilege extension to reach a high-privilege part of the browser. Other researchers have reported related weaknesses in AI-driven browsers over the past year. For teams that rely on browser-based tools and extensions across a business, AEU-I offers security-first IT and infrastructure consulting, which can help review and reduce the attack surface these findings describe.

How to Protect Yourself

  1. Update Chrome to version 143.0.7499.192 or newer and Edge to version 150.0.4078.48 or newer if you use those browsers.
  2. For Comet, Opera Neon and Claude in Chrome, keep the software up to date and review the extensions you have installed, removing any you do not recognise.
  3. Only install browser extensions from trusted sources and check the permissions they ask for, especially those that can change web pages or network traffic.
  4. If you use an AI assistant inside your browser, watch for security updates from the browser or extension maker and install them promptly.
  5. Regularly open your browser's extension list and disable or delete extensions you no longer use.

Vulnerabilities & Fixes

Terms Explained

  • browser extension A small add-on program that runs inside your web browser to add features or change how pages behave.
  • AI assistant Software built into a browser or extension that can see the screen and take actions like a digital helper.
  • CVE A public ID number given to a known security weakness so everyone can track and fix it.
  • declarativeNetRequest permission A browser permission that lets an extension change how the browser sends and receives network traffic.
  • race condition A timing flaw where a program can be tricked by quickly switching between two states at the wrong moment.
  • Known Exploited Vulnerabilities catalog A US government list of security weaknesses that are known to be used in real attacks.

Related AEU services