uBlock Origin Element Picker Flaw: How to Check You’re Patched

A high-severity uBlock Origin bug disclosed on 15 November 2026 let a website hijack the element picker and run code on other sites after one click. What happened, which versions are safe and how to check your browser and filters.

Reviewed by Mindloop Editorial on . Every link in the Sources section at the end was re-checked that day.

Mindloop card graphic with the headline uBlock Origin flaw: check you're patched, beside a browser window and a terminal reading v1.76.4

uBlock Origin is the ad blocker people install when they want their browser to be safer. That is why a flaw disclosed on 15 November 2026 caught attention. It let an ordinary-looking website turn uBlock Origin’s own element picker into a way to run code on other sites, and all it needed was one click from you.

Key takeaways

  • A uBlock Origin bug disclosed on 15 November 2026 let a website run its code on other sites after one click.
  • The attack drove the element picker from a hidden frame and slipped in a trusted, script-injecting filter.
  • Version 1.75.4 is listed as patched; be on uBlock Origin 1.76.4 or uBlock Origin Lite 2026.1110.1816.
  • After updating, check the My filters tab for script rules you never added and delete them.

The fix has been out for almost two weeks, and Firefox should already have installed it for you. Here is what the bug was, who it affected, and how to check in about two minutes that your copy is patched and clean.

What was found

On 15 November, security researcher Smitty van Bodegom published a write-up titled “Universal XSS in uBlock Origin from website-driven element picker“. On the same day, uBlock Origin’s developer Raymond Hill published the matching GitHub security advisory and rated it high severity. The story reached the front page of Hacker News within hours.

“Universal XSS” (cross-site scripting) means a page can run its own JavaScript inside other websites, not just inside itself. In a browser that is about as serious as web bugs get, because the injected code runs with your logged-in session on whatever site it targets.

The researcher says an AI model did a lot of the legwork. “GPT-5.6 Sol did most of the hard work of finding the issue,” the post says. The researcher then checked the issue themselves, and Claude wrote most of the proof-of-concept code. The report went to the developer by email on 1 November, and the details were kept private until the fixed versions had shipped.

By the numbers

1 NovemberBug reported to the developer

15 NovemberDetails made public

1.76.4Current uBlock Origin release

How the attack worked

The element picker is the tool you open by right-clicking a page and choosing to block an element. It loads a small uBlock Origin page inside the website you are on, and that page can tell the extension to save a new filter.

According to the advisory, the problem in the Firefox (Manifest V2) version came down to three things:

  1. The picker’s address could be found. Firefox gives each installed extension a random internal ID. A malicious page could learn uBlock Origin’s ID through a feature of some default filters that serve a harmless stand-in script from inside the extension.
  2. The picker trusted whoever talked to it. With the address, the page could embed the picker itself, hidden from view, and send it instructions. The picker did not check that the messages came from uBlock Origin.
  3. Picker filters were treated as trusted. The page could slip an extra rule into the filter being saved. Filters created with the picker count as trusted, and trusted filters are allowed to inject scripts into web pages.

Put together, a page only had to get you to click somewhere on it, for example over an invisible “Create” button. It could then save a rule that runs its code on a completely different site the next time you visit it. The researcher writes that they did not build the click-trick part, and neither the write-up nor the advisory reports any attacks in the wild.

The advisory notes that on Manifest V2 builds for Chromium browsers, the same trick could also leak a long internal secret. The researcher also says that a “similar but less problematic issue” affected uBlock Origin Lite, the Manifest V3 version.

Layer diagram of the three weaknesses behind the uBlock Origin element picker flaw: leaked address, trusting picker, trusted filters

Which versions are safe

The advisory lists 1.75.2 and lower as vulnerable and 1.75.4 as patched. The fixes landed in stages:

VersionDateWhat changed
1.75.22 Nov 2026First fix (the researcher then found a way around it)
1.75.43 Nov 2026The picker only starts with a verified secret token
1.76.08 Nov 2026The picker checks filters before saving them
1.76.415 Nov 2026Current release, with fixes for other reported issues

For uBlock Origin Lite, release 2026.1110.1816 includes a change that requires a valid secret before its interactive tools open. The Chrome Web Store listing showed that version on 16 November.

The simple rule: be on uBlock Origin 1.76.4 or uBlock Origin Lite 2026.1110.1816, or anything newer. The Firefox Add-ons listing for uBlock Origin showed version 1.76.4 on 16 November. Version 1.76.4 also includes fixes for other reported security issues, so it is worth having even though this bug was fixed earlier.

How to check and update in Firefox

Firefox updates add-ons on its own by default, so most people are already patched. To make sure:

  1. Click the menu button, then Extensions and themes, and select Extensions.
  2. Click uBlock Origin to open its details. The version number is listed there.
  3. If it is older than 1.76.4, go back to the Extensions list, click the gear icon in the upper-right corner and choose Check for Updates.
  4. While the gear menu is open, check that Update Add-ons Automatically is ticked. Mozilla’s update guide covers the same options.

You can also type about:addons into the address bar to jump straight to the Extensions page.

The More information box on uBlock Origin's Firefox Add-ons page, showing version 1.76.4, last updated November 15, 2026
On uBlock Origin's Firefox Add-ons page, the More information box shows the current version: 1.76.4 on November 16, 2026. Screenshot: Mindloop Experience.
Flow diagram of four steps to check and update uBlock Origin in Firefox

How to check in Chrome, Edge and Brave

Chromium browsers update extensions automatically too. To see which version you have:

  1. Open the extensions page: chrome://extensions in Chrome or Brave, edge://extensions in Edge.
  2. Find uBlock Origin or uBlock Origin Lite and click Details to see the version.
  3. If you use uBlock Origin Lite, compare it with the version on its Chrome Web Store listing. If yours is older, restarting the browser usually lets the pending update install.

If you installed the full uBlock Origin from a downloaded package rather than a store, check it the same way and, if needed, get 1.76.4 from the project’s official release page.

Did you know?

uBlock Origin Lite uses date-style version numbers, so 2026.1110.1816 is the release that requires a valid secret before its interactive tools open.

Check your filters for anything you didn’t add

Updating stops the attack from happening again, but it does not remove a rule that was already saved. Filters you create with the element picker are kept as your own custom filters, so look there:

  1. Click the uBlock Origin icon, then the gear (cogs) icon to open the dashboard.
  2. Open the My filters tab and read through the list.
  3. Look for lines you don’t remember adding, especially ones containing ##+js( with trusted- in them. Those are script-injecting rules.
  4. Delete anything unfamiliar and click Apply changes.

Most people’s list is empty or holds a few simple rules they made to hide annoying page elements. The uBlock Origin wiki explains that trusted filters “can directly execute code on web pages”. It also explains why the option called Allow custom filters requiring trust should stay off unless you know exactly why you turned it on.

Did you know?

Filters created with the element picker count as trusted, and trusted filters are allowed to inject scripts into web pages. That is why one hidden click was enough.

Common errors and fixes

  • “Check for Updates” says no updates were found, but I’m on 1.76.2. Store releases can take time to reach everyone. Try again later, or install 1.76.4 straight from the Firefox Add-ons listing.
  • My Lite version number is a date, not 1.76.x. That is normal. uBlock Origin Lite uses date-style versions like 2026.1110.1816.
  • The extension shows as disabled after an update. Some browsers turn an extension off when it asks for new permissions. Turn it back on from the extensions page and review the permission prompt.
  • I can’t see a My filters tab in uBlock Origin Lite. The My filters steps above are for the full uBlock Origin. Lite has its own settings page, and keeping it on the current version is the main step.

What it means for you

The takeaway isn’t “stop using ad blockers”. uBlock Origin fixed the problem within days of the report, and the fix reached users before the details went public, which is how disclosure is supposed to work. The broader lesson is that every extension you install can see your web pages, so its bugs become your bugs.

A short routine covers most of the risk:

  • Keep automatic extension updates switched on in every browser you use.
  • Remove extensions you no longer use. Fewer extensions means fewer things that can break.
  • Install extensions only from the official store listing or the developer’s own release page.
  • Keep your browser itself patched. Our guide to Chrome zero-days shows how to check that in a minute.
  • Be wary of pages that push you to click somewhere for no clear reason. The same caution helps with tricks like hijacked short links.

If you look after accounts that an injected script could abuse, a quick GitHub account audit is a good habit as well. More step-by-step guides like this live in Software & How-To.

Facts in this article are as of 16 November 2026.

Frequently asked questions

Is uBlock Origin safe to use now?

Yes, on a current version. The advisory lists 1.75.4 as patched, later releases added more hardening, and 1.76.4 was the current release on 16 November 2026. Keep automatic updates on.

How do I check my uBlock Origin version?

In Firefox, open Extensions and themes and click uBlock Origin to see its details. In Chrome, Edge or Brave, open the extensions page and click Details on the extension.

Was uBlock Origin Lite affected?

The researcher says a similar but less problematic issue affected uBlock Origin Lite. Its 2026.1110.1816 release requires a valid secret before its interactive tools open.

Do I need to do anything besides updating?

Updating stops new attacks but does not remove a rule already saved. Open the My filters tab in the uBlock Origin dashboard and delete any script rules you never added.

Quick quiz

What did the attacker page need from the user?

  • Their password
  • A single click on the page
  • Permission to install software

Once the hidden picker was loaded, one click on the page, for example over an invisible Create button, was enough to save the rule.

Which version does the advisory list as patched?

  • 1.75.2
  • 1.74.0
  • 1.75.4

1.75.2 and lower are listed as vulnerable and 1.75.4 as patched, after the researcher got around the first fix.

Where should you look for rules you did not add?

  • The My filters tab
  • The browser history
  • The Chrome Web Store

Filters made with the element picker are kept as your own custom filters, which the My filters tab lists.

Sources

Written by Mindloop Editorial

The Mindloop Experience editorial team writes clear, carefully sourced explainers and how-tos on AI and technology, software and the business of tech, for anyone who likes to know how things actually work.

Meet the editorial team

Responses

Write a response

More from Mindloop Experience

See all from Mindloop Experience

You can clap up to 50 times.