The maintainer of uBlock Origin, Raymond Hill, writing as gorhill, disclosed on 15 November a high-severity flaw in the add-on’s Firefox element picker. In a GitHub security advisory, he said “it’s possible for a webpage to iframe the element picker and control it to add arbitrary trusted filters when a user clicks on the webpage.” Versions 1.75.2 and lower are listed as affected. The first fix shipped in 1.75.4 on 3 November; further changes followed in 1.76.0 on 8 November. The advisory’s brief advice is to update to 1.76.0 or later.
No exploitation of the flaw was reported in the advisory or in the researcher write-up reviewed for this article, and no CVE identifier was seen in those sources.
What was fixed, and when
The element picker is the tool that lets a user point at a part of a page and create a filter to hide it. The advisory describes a way for a webpage to place that picker in an iframe and, if the user then clicks on the page, to add trusted filters that the add-on would treat as the user’s own. Trusted filters, as researcher Smitty van Bodegom (loops) wrote in a 15 November post, “can inject JavaScript code into pages.” The practical risk, in the sources’ own terms, is a universal cross-site scripting path: a visit and a click could be enough for filters to run with the add-on’s trust, including the ability to run script in pages the user later opens. This article does not reproduce the demonstration.
Hill’s advisory lists two layers of fix. Version 1.75.4, released on 3 November, introduced a secret token intended to stop a page from driving the picker in that way. Version 1.76.0, released on 8 November, added validation of the filter and a block on war:-related filters. The 15 November disclosure therefore comes after both patches were already in released builds. The recommended version remains 1.76.0 or later, not 1.75.4 alone.
Van Bodegom also wrote that “a similar but less problematic issue also affected the MV3 version, uBO Lite.” That comparison is the researcher’s. The GitHub advisory is written against the classic uBlock Origin releases named above.
How the issue was found
The same write-up is candid about the discovery process. Van Bodegom said “GPT-5.6 Sol did most of the hard work of finding the issue,” and that “I then checked and verified the issue.” That is the researcher’s account of how the bug was found, not an official claim by the uBlock Origin project, and it should be read as such. The advisory itself is the vendor’s confirmation of the flaw, the affected versions, and the patches.
The mechanism sits in a family of interface bugs in which a preview or picker surface can be steered by a page the user is looking at. TSN has previously covered a now-fixed flaw in Claude Code Desktop’s preview pane that allowed local secrets to be read. Browser add-ons have their own history of trust problems, including Socket’s report on Chrome extensions that hijacked searches and a Fearless Wallet extension leak of users’ private keys. Those are neighbouring cases about extension and preview trust, not the same bug.
A shipped patch is not evidence of exploitation
The public record on 16 November is a vendor advisory and a researcher write-up, not a report of attacks in the wild. Hill has classified the issue as high severity, named the affected builds, and pointed users to 1.76.0 or later. Van Bodegom has described what trusted filters can do and has said a less serious variant was present in uBO Lite. Neither source says the flaw was used against people.
That distinction should govern how the disclosure is read. A universal XSS in a widely installed content blocker is serious because of what it could allow, not because a campaign has been documented. The absence of a reported exploitation, and of a CVE in the sources reviewed here, is not a guarantee that nobody tried the bug before the 3 November token fix. It is only an absence in the present record.
The update advice is accordingly ordinary and specific. People still on 1.75.2 or earlier should move to 1.76.0 or a later build. People already on 1.75.4 have the first fix, but the advisory still points to 1.76.0 because of the extra filter checks added five days later. This article does not walk through the click path or publish a test page, because those details are not needed to take the only practical step the maintainer has asked for: install the patched release.
Sources
- gorhill, GitHub security advisory GHSA-cmqw-9r2w-6wv2, 15 November 2026
- Smitty van Bodegom (loops), “uBlock Origin universal XSS,” 15 November 2026
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
- Noma Labs Details “SneakPeek”, a Now-Fixed Flaw That Let Claude Code Desktop’s Preview Pane Read Local Secrets is the closest TSN neighbour: a user-interface surface that could be abused when the user was looking at untrusted content.
- Socket Says 319 Chrome Extensions Hijacked Searches: How to Check
- Fearless Wallet Extension Leaked Users’ Private Keys, Polkadot Says
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X





