uBlock Origin versions 1.75.2 and lower on Firefox had a high-severity flaw that let a malicious web page add its own "trusted" filters when you clicked on it, according to the maintainer's GitHub security advisory published on November 15, 2026. Trusted filters can run JavaScript on other websites, so this was a way to inject code into any site you later visited. The fix has already shipped. Your only job is to confirm you are on 1.76.0 or later.
What the uBlock Origin vulnerability let a page do
The advisory, titled "Universal XSS from website-driven element picker" and rated High, says that on the Firefox MV2 extension a webpage can load uBO's element picker in an iframe and drive it to add arbitrary trusted filters when the user clicks on the page.
The element picker is the tool you use to point at an ad and block it. Normally only you drive it. Here, a hostile page could drive it instead.
The researcher who found it, Smitty van Bodegom, explains the chain in his write-up:
- The page first leaks the extension's random per-install ID. One route uses a default filter rule that makes uBO send a request to its own extension URL, which the page can intercept. He says other leak routes exist.
- It loads the picker page in an invisible iframe and sends it messages.
- One field in those messages was not checked, so a newline could smuggle in a second filter, such as a trusted scriptlet filter.
- The user then has to click the invisible "Create" button. He did not build that part, but says an overlay or a fully transparent button would do it, and that any click on the page would be enough.
The damage lasts. He writes that filters added through the picker stay trusted until a recompile, and an attacker could open the target site straight away, so editing your custom filters afterwards does not help much.
This is a one-click attack, not a zero-click one. Neither the advisory nor the write-up says it was used against anyone. It is a researcher-reported flaw with a public proof of concept, and that demo only works on Firefox.
Which uBlock Origin builds are affected
Confirmed: the Firefox MV2 build. The advisory lists 1.75.2 and lower as affected.
Less clear: the advisory notes that on MV2 Chromium the attacking page could also extract a long secret used for the extension's web-accessible resources. But only the Firefox exploit was demonstrated.
uBO Lite: the advisory does not mention it. The researcher says a "similar but less problematic issue" affected the MV3 version, uBO Lite, and that the issue is fixed. He gives no further detail, so treat that as his account rather than an official scope statement.
Why 1.76.0, not 1.75.4
The advisory lists 1.75.4 as the patched version. But the fixes landed in stages, per its timeline:
- November 1: the researcher reported the bug by email.
- November 2: 1.75.2 changed how scriptlets use XHR methods.
- November 3: 1.75.4 made the element picker launch only with a verified secret token.
- November 8: 1.76.0 added validation of filters created in the picker and blocked war:-related filters "for the time being".
The email thread in the advisory also shows the researcher found a second way to leak the extension ID on November 2, and suspected a possible race-condition bypass he could not reproduce consistently. Given that, 1.76.0 or later is the safer target, since it includes the extra hardening.
How to check your uBlock Origin version in Firefox
- Type
about:addonsin the Firefox address bar and press Enter to open the Add-ons Manager. - Select Extensions in the left sidebar.
- Click uBlock Origin and read the version number in its details.
- If the version is below 1.76.0, click the gear menu at the top of the Add-ons Manager and choose Check for Updates.
- Go back to uBlock Origin's details and confirm the version is now 1.76.0 or later.
Firefox normally updates extensions on its own, so most people are probably already covered, but a quick look is cheap.
If you want to know why the details came out only now: the advisory says the maintainer held them back until a stable release shipped.
Is uBlock Origin safe to keep using?
Yes, on a patched version. The bug was reported privately, fixed within days, and disclosed after the fix. Nothing in the advisory or the write-up points to attacks in the wild. The advisory page also has no CVE ID.
One odd detail: van Bodegom says GPT-5.6 Sol found the bug and he verified it, with Claude writing most of the proof-of-concept code.
What to watch next
The 1.76.0 change that blocks war:-related filters is described as "for the time being". Watch for a later uBlock Origin release that lifts it, since that will show whether the maintainer settled on a permanent fix for that part of the attack.