Tor Relays After the 0.4.9.14 Security Release

Home › Guides › Tor Relays After the 0.4.9.14 Security Release

✓ checked 28 October 2026 · source: Tor Project Onionoo (relay list published 2026-10-28 16:00 UTC); Tor release notes · method · caveats · download the data

Three weeks after the Tor Project released security version 0.4.9.14, 76.0% of running Tor relays use it or the newer 0.4.9.15. That is 6,997 of 9,208 relays in the Tor Project’s Onionoo relay list for 28 October 2026, carrying 74.8% of the network’s consensus weight, the measure Tor uses to decide how much traffic each relay gets. Exit relays upgraded fastest (88.4%).

Running relays: 9,208On 0.4.9.14 or 0.4.9.15: 6,997Marked obsolete: 1,140

Why this matters

Tor relays are the volunteer-run servers that carry Tor traffic; exit relays are the last hop, where traffic leaves for the open web. The Tor Project released 0.4.9.14 on 7 October 2026 and described it as fixing “high severity issues” in all Tor components. According to its release notes, the fixes include a bug that let a client crash a relay with a crafted conflux link cell, a flaw that let clients use MiddleOnly relays in roles they should not have (TROVE-2026-067), expired family certificates being ignored (TROVE-2026-062), and a directory authority rule on relays per address (TROVE-2026-064). Relays that have not upgraded still run code with these bugs.

Upgrade share by relay type

Relay typeRunningOn 0.4.9.14 or 0.4.9.15Share
Exit relays2,7492,43188.4%
Guard relays3,9852,97474.6%
Onion service directories (HSDir)2,8792,03970.8%

Guard relays, the entry point for most Tor users, and onion service directories lag exits by more than ten percentage points. A relay can carry several flags, so the rows overlap.

Most common versions

Tor versionRunning relaysShare
0.4.9.146,99275.9%
0.4.9.117338.0%
0.4.9.135435.9%
0.4.9.124725.1%
0.4.9.91191.3%
0.4.9.81051.1%
0.4.9.6870.9%
0.4.9.5730.8%

The largest group not yet upgraded runs 0.4.9.11 (733 relays), a June 2026 release. Onionoo marks 1,140 relays as running an obsolete version, meaning one the directory authorities no longer recommend. Versions 0.4.9.12 and 0.4.9.13 are still listed as recommended even though 0.4.9.14 fixes security bugs in them.

The Tor Project released 0.4.9.15 on 28 October 2026, the day of this snapshot, and 5 relays already ran it. Its release notes say it adds defences against floods of directory requests and that, because of new required protocol features, “Tor versions 0.4.8 and earlier will no longer work on the network.” 2 running relays were still on 0.4.8.

For changes in the exit network earlier this month, see Tor exit relays fell 11% in four days. For Tor use under censorship, see Tor users in Azerbaijan and Snowflake requests from Iran.

Method

We downloaded the Onionoo details document for all running relays on 28 October 2026 (relays published 2026-10-28 16:00 UTC) and grouped relays by the Tor version they report. “Upgraded” means a relay reports exactly 0.4.9.14 or 0.4.9.15; development builds such as 0.5.0.0-alpha-dev (51 relays) are counted as not upgraded because their code cannot be matched to a release. Consensus weight shares use Onionoo’s consensus_weight_fraction. Release dates and fix descriptions come from the Tor ReleaseNotes file and the Tor Project forum announcement.

Caveats

  • The version is what each relay reports. Distributions such as Debian can backport fixes into a package that keeps an older version number.
  • This is a single snapshot. The relay list changes hourly, and the Tor Project does not publish past versions in Onionoo, so we cannot show the upgrade curve day by day.
  • Not upgraded does not mean exploited. The Tor Project said the detailed tickets would stay private for at least a week after release.

Download the data

Cite as: ProxyPicker, “Tor Relays After the 0.4.9.14 Security Release”, 28 October 2026, https://proxypicker.com/tor-relay-upgrades/. Source data: Tor Project Onionoo (CC0).

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.