Skip to content

uBlock Origin Fixes a Flaw That Let a Website Run Code on Any Site You Visit

Miklos Zoltan

By Miklos Zoltan . 16 November 2026

Founder - PrivacyAffairs

Laura Bede

Fact-Checked this

Until early November, one click on the wrong website could turn uBlock Origin against you.

The popular ad blocker had a flaw that let a malicious page add its own rule to the extension. That rule could then run the attacker’s code on any other website you opened, your bank or webmail included. Security people call this a universal cross-site scripting (UXSS) bug.

It’s fixed. Raymond Hill, who develops uBlock Origin, shipped the main fix on 3 November and published the advisory on 15 November, rating it high severity. The researcher who found it, Smitty van Bodegom, explained the attack the same day. When we published, the story had reached Hacker News and Lobsters, but we found no reports from major outlets.

Most people are already safe, because browser extensions update themselves. It takes a minute to make sure.

What the Flaw Let a Website Do

uBlock Origin has an element picker: you right-click something on a page, pick it, and the extension writes a rule that hides it. The picker runs inside a small frame that the extension places on the page.

A malicious site could load that frame itself, make it invisible and feed it instructions. The picker didn’t check who was talking to it. So the page could fill in a rule of its choosing and wait for you to click anywhere, which pressed the hidden “Create” button.

That alone would only hide elements. The problem was what kind of rule got through. uBlock Origin supports “trusted” rules that can inject scripts into pages. They exist to defuse ad and tracking scripts, and the extension normally accepts them only from its own filter lists. Rules made with the element picker were treated as trusted, and the attacker could smuggle one in. A trusted rule for, say, google.com would run the attacker’s script whenever you opened google.com.

To find the picker in the first place, the page needed a value unique to each installation of the extension. Van Bodegom showed it could be read out through one of uBlock Origin’s own default rules. That same value is also an identifier that stays the same across websites, which is a privacy problem of its own (more on that in our browser fingerprinting guide).

The researcher’s demo targets uBlock Origin on Firefox. His report says the trick could also extract the equivalent secret in the Chromium version (used in Edge, Opera and Brave). uBO Lite, the newer version built for Chrome’s extension rules, had what van Bodegom calls a similar but less problematic issue.

We found no report of anyone using the flaw against real users.

Which Versions Are Safe

For the full uBlock Origin, 1.75.4 is the line. Anything from 1.76.0 on also carries the later hardening.

Extension
Affected
Safe
In the store (16 Nov)
uBlock Origin on Firefox (desktop and Android)
1.75.2 and older
1.75.4 or later
1.76.4
uBlock Origin on Edge, Opera or Brave
1.75.2 and older
1.75.4 or later
Edge 1.76.2, Opera 1.76.0
uBO Lite (Chrome, Edge, Firefox, Safari)
A similar, smaller issue
2026.1110.1816 or later
2026.1110.1816 (Edge)
uBO Lite’s fix version is our reading of the code history: the same kind of safeguard (a secret the page can’t know) was added on 3 November and first shipped in 2026.1110.1816. Brave serves its own copy of uBlock Origin, so check its version on brave://extensions. The full uBlock Origin was removed from the Chrome Web Store on 31 August 2026; on Chrome, the version you can install is uBO Lite. Store versions as listed when we checked.
Sources: uBlock Origin security advisory GHSA-cmqw-9r2w-6wv2, uBlock Origin and uBO Lite release notes, Firefox, Edge and Opera add-on stores, Chrome’s Manifest V2 timeline. Checked 16 November 2026.

How to Check and Fix It

  1. Check the version. In Firefox, type about:addons in the address bar and select uBlock Origin. In Edge, Opera, Brave or Chrome, open the extensions page (edge://extensions, opera://extensions, brave://extensions, chrome://extensions) and look at the uBlock Origin or uBO Lite entry. The version number is listed there.
  2. Update if it’s old. In Firefox, click the gear icon on about:addons and choose “Check for Updates”. In Chromium browsers, switch on Developer mode on the extensions page and click “Update”. Restart the browser if the number doesn’t change.
  3. Look at your own rules. This is the step most people skip. Open uBlock Origin’s dashboard (the dashboard button in its pop-up) and go to “My filters”. Rules made with the element picker land there. If you see lines you didn’t write, especially ones containing “+js(“, delete them and click “Apply changes”. If the list is empty or every line is yours, you’re done.

How It Was Found, and How Fast It Was Fixed

Van Bodegom reported the bug by email on 1 November. The advisory shows Hill committed a first fix the next day. The researcher found a way around it within hours, and version 1.75.4 went out on 3 November. It only opens the element picker when the request carries a secret the page can’t know.

Later releases tightened things further: 1.76.0 (8 November) checks every rule before the picker creates it and, for now, switches off the type of filter that leaked the secret value. Versions 1.76.2 and 1.76.4 (13 and 15 November) added more security changes. Hill published the details only after the fixed versions were out, which is how coordinated disclosure is supposed to work. From report to stable fix took two days, for an extension built largely by one developer and given away for free.

Van Bodegom writes that an AI model, OpenAI’s GPT-5.6 Sol, did “most of the hard work” of finding the issue after he asked it to look for one. He checked it himself, and he says Claude wrote most of the proof-of-concept code. Here the model pointed, a human checked, and the maintainer fixed it fast.

Should You Still Use an Ad Blocker?

Yes. An ad blocker sees and edits every page you open, so a bug in one is serious, and this one was. But ads themselves remain one of the common ways malware reaches ordinary people: earlier this month a hacked ad system served iPhone-attack code on Dutch news sites. Blocking that traffic still protects you far more often than the blocker puts you at risk.

What matters is keeping the extension current and installing it only from the official add-on stores. Dropping uBlock Origin over this would be like giving up seatbelts after a recall of one buckle.

We have asked Raymond Hill whether he knows of any attacks using the flaw and which uBO Lite release carries the fix. We’ll update this article if he answers.

Our Mission

We believe security online security matters and its our mission to make it a safer place.