Key details

  1. Released 29 October 2026 for desktop and Android.
  2. First stable Tor Browser based on Firefox ESR 153.
  3. More than 270 upstream Bugzilla issues reviewed and addressed for possible Tor privacy/security impact; not 270 reported CVEs.
  4. Stable Linux AArch64 builds now available; 32-bit x86 Linux builds discontinued.
  5. Project reports approximately 200 daily 32-bit Linux update checks, versus approximately 4,000 in 2019.
  6. Generic window titles are optional and disabled by default because of accessibility and window-manager compatibility concerns.
  7. Bundled Tor updated to 0.4.9.15; NoScript updated to 13.6.37.1984.

What builders should take away

  1. If packaging or deploying Tor Browser on Linux ARM64, move from Alpha to the stable 16.0 release unless specifically testing prereleases.
  2. Audit 32-bit x86 Linux endpoints; they no longer receive new stable Tor Browser builds from 16.0 onward.
  3. Preserve and retest managed browser privacy settings after the Firefox ESR migration, particularly policies touching fingerprinting and proxy behaviour.
  4. Do not enable generic window titles fleet-wide without checking screen readers, accessibility tooling and window-switcher behaviour.
  5. Do not equate an upstream privacy audit with a guarantee against tracking, endpoint compromise or all browser vulnerabilities.

What changed

On 29 October 2026, the Tor Project released Tor Browser 16.0 for desktop and Android, rebasing the stable browser on Firefox ESR 153. The project reports reviewing and addressing more than 270 Bugzilla issues related to changes in upstream Firefox that could affect Tor Browser privacy and security; this is an audit scope, not a claim that 270 vulnerabilities were patched. Stable native AArch64 Linux builds now support ARM machines including Raspberry Pi and Apple Silicon systems running Linux. At the same time, 32-bit x86 Linux builds are discontinued. Desktop Settings were redesigned, a generic-window-title privacy option was added but left disabled by default, and the bundled Tor daemon moved to 0.4.9.15.

Why it matters

Tor Browser is not a cosmetic Firefox fork: upstream browser behaviour can change fingerprintability, proxy routing and other privacy assumptions. The ESR migration and audit matter to people relying on Tor's anonymity guarantees, while AArch64 support changes which Linux devices can run the stable browser. Maintainers of older 32-bit Linux installations need a migration path rather than assuming security updates will continue. The optional generic-title feature also exposes a trade-off between hiding page titles from local software and preserving screen-reader and window-manager compatibility.

A Firefox ESR transition is also a privacy compatibility audit

The project says its annual migration review covered more than 270 Bugzilla issues involving Firefox changes with potential privacy or security consequences. That number measures review scope, not confirmed vulnerabilities or exploitation. Tor Browser 16.0 is the first stable build on Firefox ESR 153, carrying a year's upstream changes into the hardened browser.

Linux ARM64 becomes stable; 32-bit Linux reaches the end

After roughly a year in testing, AArch64 Linux users can use the stable Tor Browser channel on supported devices. Conversely, Tor Browser 16.0 stops producing 32-bit x86 Linux builds, following Firefox. The project reports about 200 daily update checks from 32-bit Linux, down from roughly 4,000 in 2019. Operators should inventory older endpoints and move to 64-bit hardware or operating systems where possible.

Window-title protection is useful but opt-in

A new setting replaces the title of the current webpage in the window chrome with a generic 'Tor Browser' label. Other local applications can normally read those titles, so the feature can reduce incidental disclosure of visited pages. It remains disabled by default while the team evaluates side effects for screen readers, desktop window managers and app switchers. This is not protection against a compromised host.

Settings and Android packaging change

The desktop settings redesign separates Appearance, Downloads, Tabs and browsing, Accessibility and Languages, while rebuilding Tor-specific Connection and Security Level panels. Existing preferences are preserved. On Android, interface components adopt more Material Design 3 patterns and resource compression helps the app remain under Google Play's 100 MB APK limit.

What to watch next

  • Privacy or compatibility regressions reported after the ESR 153 migration.
  • Any accessibility fixes that let generic window titles become a safer default.
  • Tor Browser 16.x patch releases and the status of ARM64 Linux builds.
  • Whether remaining 32-bit Linux deployments migrate or lose current browser security support.

Still unclear

  • The project does not quantify real-world anonymity improvement from the 270-plus-issue audit.
  • The window-title feature has unmeasured accessibility and desktop-integration side effects.
  • ARM64 stability and performance on every supported Linux distribution have not been independently benchmarked here.

Sources

Direct reading behind this dossier.

3 sources
New Release: Tor Browser 16.0
The Tor Project primary announcement

Release details, ESR 153 migration, 270-plus issue audit, Linux architecture changes, window-title privacy option and Android changes.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment