A uBlock Origin vulnerability let a malicious webpage add arbitrary trusted filters to the Firefox MV2 extension. According to the security advisory, this worked when a user clicked anywhere on the page. It also required a filter rule with a prevent-xhr or prevent-fetch scriptlet that fulfills the response with a WAR, a web accessible resource.
Is this a uBlock Origin XSS issue? The reporter, who goes by syvb, emailed it on 1 November 2026 under the subject “Universal XSS from website-driven element picker”. XSS means cross-site scripting, where an attacker runs their own code on a site. Here the page embeds the element picker in an iframe and controls it.
First, the attacker’s site hooks XHR, the browser mechanism for web requests, to extract the extension UUID. On MV2 Chromium it can also extract the long WAR secret. With that, the page sends messages to the element picker. Filters added by the element picker are always treated as trusted, at least until a recompile.
The reporter also showed that the filter displayed can differ from the filter actually added. The opt field is not validated, so a second filter can be smuggled in. A website could also overlay content on the embedded picker or make the iframe invisible.
Raymond Hill, who responded to the report for uBlock Origin, committed a first fix on 2 November 2026, published in version 1.75.2. Version 1.75.4 followed on 3 November and launches the element picker only with a verified secret token. Version 1.76.0 on 8 November validates the new filter and prevents war-related filters for the time being.
The first fix did not close every route. Syvb noted that the extension UUID could still be obtained by defining a responseText getter on the XHR prototype. The reporter also suspected a bypass if the page races to inject into an iframe first, but could not reproduce it consistently.
Your next step is simple. Check that your Firefox extension runs version 1.76.0 or later, since this uBlock Origin security update includes all four related commits. User clicks were enough for the attack, so keep your extensions updated.
Read github.com article for more information.