A malicious web page could trick uBlock Origin on Firefox into adding filters that run JavaScript on other websites. The extension’s maintainer rates the bug High. The Firefox add-on has about 11.5 million users, according to its Mozilla Add-ons listing.
The flaw is fixed. Even so, several follow-up security releases shipped over two weeks. The safest move is to check that your copy runs version 1.76.4, the current release on Mozilla’s site.
What happened
Raymond Hill, who develops uBlock Origin under the name gorhill, published GitHub security advisory GHSA-cmqw-9r2w-6wv2 on November 15, 2026. It is titled “Universal XSS from website-driven element picker.” No CVE number is listed.
The advisory lists versions 1.75.2 and lower as affected. It names 1.75.4 as the patched version. A researcher known as syvb reported the issue by email on November 1.
The researcher, Smitty van Bodegom, described the bug in a detailed write-up on his blog. He calls it a “one-click universal XSS issue.” In plain words, one site could plant code that later runs inside a different site, such as your webmail or bank.
He also disclosed how he found it. He writes that OpenAI’s GPT-5.6 Sol “did most of the hard work of finding the issue.” He says he verified the finding, and that Anthropic’s Claude wrote most of the proof-of-concept code.
What changes for you
The risk depends on which version of the extension you use. The table below sums up what the sources say.
| Extension | What the sources say | What to do |
|---|---|---|
| uBlock Origin for Firefox (desktop and Android) | Main target. The researcher’s demo works only on Firefox. | Update to 1.76.4. |
| uBlock Origin (Manifest V2) on Chromium browsers | The reporter says an attacker can also extract the needed secret on MV2 Chromium. | Update, or move to a supported build. |
| uBlock Origin Lite (Manifest V3) | Hit by a “similar but less problematic issue,” per the researcher. No details given. | Keep the extension updated. |
The Chromium row matters less every month. The uBlock Origin project page notes that the Chrome Web Store removed all remaining Manifest V2 extensions on August 31, 2026. It adds that Microsoft Edge started moving consumers away from MV2 in August 2026.
How to check your version
- In Firefox, open the menu and choose Add-ons and themes, or type about:addons in the address bar.
- Select uBlock Origin and look at the version number in its details.
- If it shows anything below 1.76.4, use the gear icon and pick Check for Updates.
- Open the uBlock Origin dashboard and review the My filters tab for any entry you did not create.
The last step is a simple precaution. Filters added through the element picker land in your custom list, so an injected rule would show up there.
How the attack worked
This section explains the technical chain. General readers can skip ahead to the timeline.
The element picker is the tool you use to click on an ad and block it. uBlock Origin shows it by loading an internal extension page inside a frame on the current site. That page can tell the extension’s background script to save new filters.
The core flaw was simple. The picker page accepted messages from the web page around it, so an attacker’s site could drive it. The researcher lists four steps.
Step 1: Find the picker’s address
On Firefox, each install gets a random ID that forms part of internal extension addresses. A default uBlock Origin filter hooks the page’s fetch function and answers some requests from an internal resource. That reply goes through an address containing the ID. The attacker’s page can watch its own XMLHttpRequest calls, trigger the filter, and read the ID. The researcher says other leak paths also exist.
Step 2: Load the picker invisibly
With the ID in hand, the attacker can load the picker page in a hidden frame.
Step 3: Smuggle in a dangerous filter
The picker normally refuses scriptlet filters, which inject JavaScript. However, one field, called opt, usually holds a request type such as image. Adding a line break in that field let the attacker append any trusted filter. The advisory adds that the filter shown on screen could differ from the one actually saved.
Step 4: Get one click
The attacker can make the frame transparent or cover it with other content. A click anywhere on the page would then press the hidden Create button. The researcher did not build this last step, but he says any user click would be enough.
Why does a click matter so much? The project’s documentation on My filters warns that filters requiring trust “can directly execute code on web pages.” Normally users must switch on a setting to allow such filters in their own list. Filters saved by the picker counted as trusted, at least until uBlock Origin recompiled them.
Fix timeline
The fixes arrived in stages. The dates below come from the advisory and from the version history on Mozilla Add-ons.
| Date (2026) | Event |
|---|---|
| November 1 | syvb reports the bug by email. |
| November 2 | Version 1.75.2 stops scriptlets from using XHR methods a page could tamper with. |
| November 3 | Version 1.75.4 launches the picker only with a verified secret token. |
| November 8 | Version 1.76.0 validates filters before the picker creates them and blocks war:-related filters for now. |
| November 13 | Version 1.76.2 adds a longer delay before the picker sets up communication, plus a security change to patch fetching. |
| November 15 | The advisory and write-up go public. Version 1.76.4 “addresses remaining reported security issues.” |
The 1.76.0 release notes on GitHub list the picker validation change. They do not label it as a security fix, though.
Version 1.76.4 also removes the unused warOrigin and warSecret code. Those names refer to the web accessible resources that the attack relied on.
What remains unclear
Some details are still missing. The researcher has not explained the uBO Lite variant. The advisory also notes a possible bypass, but the reporter could not reproduce it reliably. It would need uBlock Origin to inject into a late-loading frame and the page to win a race.
Neither the advisory nor the write-up reports attacks in the wild. Still, the full method is now public. Users who have turned off automatic add-on updates should update by hand today.











