Privacy / Tails / Security
Tails 7.17.1 removes uBlock Origin after browser flaw
Tails 7.17.1 removes uBlock Origin after a cross-site scripting flaw. Check affected browser security levels and upgrade without erasing Persistent Storage.

Tails 7.17.1 is an emergency update that temporarily removes uBlock Origin from Tor Browser. Released on November 17, 2026, it addresses a flaw that could let a malicious website cause JavaScript to run inside another website. Upgrade an affected Tails USB stick and restart into the updated system. The Tor Project release notice says Standard and Safer security levels are affected, while Safest is not.
The project says it is not aware of exploitation. That statement does not establish that nobody used the flaw, but it also provides no basis for claiming that Tails users were deanonymized. The demonstrated problem concerns what a website can do inside the browser.
How one site could interfere with another
uBlock Origin's element picker lets a user create a filter for part of a page. The researcher's disclosure describes a way for a hostile page to manipulate that interface and create a trusted filter after a user clicks. Trusted filters can inject JavaScript into other pages. A malicious rule could cross the boundary that normally separates unrelated websites.
The uBlock Origin advisory lists versions 1.75.2 and earlier as affected and 1.75.4 as patched. It records further defensive changes in 1.76.0. The advisory also describes filter and scriptlet prerequisites. This was not a claim that any ordinary page visit always executed an attack without interaction.
Tails chose temporary removal of the extension for this emergency release. Follow the Tails update procedure rather than independently reinstalling an extension into Tor Browser. An upstream extension fix and an operating-system release are different distribution decisions. The release notice says uBlock Origin will return when possible, without committing to a date.
Browser data and account privacy
The immediate concern is information available to a website session. Script running in the wrong page context could read or change data that page can access. A logged-in account may contain identifying details even when the network connection uses Tor. Altered page content could also mislead someone about a payment address or the result of an action.
These browser capabilities create a risk for sensitive account activity. The sources reviewed here do not show extraction of a local wallet seed, compromise of the Monero protocol or disclosure of a user's network address. Avoid turning a browser vulnerability into a broader claim that the evidence does not support.
Monero transaction privacy cannot protect information that a user discloses to a website or account. Keep wallet secrets out of browser forms, and verify payment details in the wallet before authorizing a transfer. Our Tails, Whonix and Qubes introduction explains the different roles of temporary sessions, network routing and isolated workspaces.
Upgrade without overwriting wallet storage
Automatic upgrades are available from Tails 7.0 or later. Use the supported upgrade path for your existing USB stick. If automatic upgrading fails, follow the linked manual upgrade instructions. Installing a fresh image over the same stick is a different operation and can erase Persistent Storage.
Before changing the stick, check that you have the wallet recovery material and backups you need, stored safely away from the device being upgraded. Our Tails USB and wallet backup guide covers those preparations. Do not paste recovery words into a browser to test them, and do not assume an operating-system upgrade creates a wallet backup.

Restart and confirm the running release
Restarting Tails clears malicious uBlock Origin configuration introduced through this issue, according to the Tor Project. Restarting the old vulnerable release still leaves its software available for another attempt. Complete the upgrade and confirm that the running system is 7.17.1 or a later supported release that includes the fix.
If you have evidence that a sensitive account was affected, review it from a clean, updated environment. Consider the data visible to that account and revoke sessions where appropriate. A restart cannot recover information already copied elsewhere. We have verified the published guidance, but have not reproduced the exploit or performed a USB upgrade or wallet recovery test for this article.