Tor Project Issues Emergency Relay Update Amid DDoS Attack

The Tor Project released Tor 0.4.9.17 after a DDoS attack strained its relay network. See what the IPv6 fix changes and what relay operators should do.

Nov 18, 2026
3 minute read
eSecurity Planet content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More

The Tor Project is urging relay operators to upgrade after a distributed denial-of-service (DDoS) attack affected most of them.

The project released Tor 0.4.9.17 on Nov. 13 after a flood of client circuits overwhelmed relays across the network. The update changes how relays handle IPv6 clients when applying denial-of-service protections, and developers say they are evaluating additional defensive measures for further updates in the coming weeks.

The most significant disclosed change involves how Tor handles IPv6 clients when applying relay DoS defenses. Under the update, relays group IPv6 clients by their /64 network prefixes rather than treating individual addresses separately. This helps the software account for clients sharing the same subnet when enforcing protections.

The release also includes two directory authority changes:

  • Bastet: Tor removed its directory authority keys following concerns about a possible compromise. The authority could return with replacement keys.
  • Maatuska: The project updated its IP addresses.
Advertisement

These changes add another security dimension to the release beyond its immediate response to the circuit flood.

An emergency patch does not mean the attack is over

The timing of version 0.4.9.17 is important. Tor issued another emergency update on Nov. 4 to address excessive directory requests generated by outdated clients caught in restart loops.

The latest release suggests that protecting the network remains an active challenge rather than a problem solved by one software update.

Reports from relay operators also indicate that the disruption has continued. SecurityWeek cited an operator who described relays becoming unresponsive after the latest update, with one losing its HSDir status during an attack.

Tor has not publicly identified the attackers, disclosed traffic volumes or confirmed that the latest defenses have stopped the campaign.

What Tor users should expect

Although the upgrade instruction targets relay operators rather than ordinary Tor Browser users, the attack affects everyone relying on the network.

Advertisement

Tor depends on volunteer-operated relays to move traffic between users and destinations. When those servers become overloaded, users could experience slower connections, unreliable access to onion services or temporary availability problems.

There is also a distinction between network security and browser security. Tor 0.4.9.17 is a relay software release, not a newly announced Tor Browser update. Ordinary users should not assume they need to download a different browser version because of this announcement.

Relay operators face an urgent upgrade

The Tor Project has asked relay operators to install version 0.4.9.17 as soon as possible. The update requires no additional configuration changes. After restarting the service, operators should:

  • Verify the active build. Confirm the running Tor process reflects version 0.4.9.17 and has resumed forwarding traffic.
  • Monitor stability over several hours. Compare reachability and bandwidth against normal baselines, watching for intermittent drops or lost HSDir flags even if the daemon stays up.
  • Log and report recurring disruptions. Record the exact Tor version, outage timestamps, duration, and whether the relay self-recovered.
Advertisement

Sharing those logs on the Tor Project Forum or the tor-relays mailing list gives developers vital cross-network visibility. On a volunteer-run network, comparing telemetry across independent relays is the fastest way to spot shifting attack patterns and shape follow-up defenses.

Other news: VulnCheck counted more than 100,000 vulnerability disclosures in 2026, putting pressure on patch teams to weigh active exploitation and internet exposure alongside severity scores.

Aminu Abdullahi

Aminu Abdullahi

Content Writer

Aminu Abdullahi is a B2C and B2B technology and finance writer with more than six years of experience covering enterprise IT, cybersecurity, cloud computing, artificial intelligence, fintech, business software, and emerging technologies. His work has appeared in publications including TechRepublic, eWEEK, Channel Insider, Geekflare, Enterprise Networking Planet, eSecurity Planet, CIO Insight, and Webopedia. With a technical background in computer science, he specializes in translating complex technology topics into clear, accessible content for business leaders and decision-makers.

eSecurity Planet Logo

eSecurity Planet is a leading resource for IT professionals at large enterprises who are actively researching cybersecurity vendors and latest trends. eSecurity Planet focuses on providing instruction for how to approach common security challenges, as well as informational deep-dives about advanced cybersecurity topics.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.