Tor Project ships 0.4.9.17 as ongoing DDoS circuit-flooding attack on relays continues; operators report HSDir impact
Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 2 fontes trouxeram em 16/11/2026 12:05; os links antigos trazem para cá.
Fontes: securityweek.com ↗ gbhackers.com ↗
The Tor Project released Tor 0.4.9.17 on November 13, 2026 as a rapid response to an ongoing DDoS attack on the Tor network. The attackers flood volunteer relays with client circuits, exhausting memory, CPU and bandwidth and causing slowdowns or disconnections (gbhackers.com). The attack has reportedly affected most relay operators (securityweek.com). The attackers and their motives have not been identified, and neither source gives a CVE, CVSS score or attribution. The release patches several security issues, and the project says more defenses are under consideration and further versions will follow because one patch cannot fully stop the flooding (gbhackers.com, securityweek.com). As of November 16, relay operators report that the update has not ended the disruption (securityweek.com). Ordinary Tor users need no action (gbhackers.com).
Detalhes técnicos
- The attack creates a very large number of client circuits across the network. A single relay can receive hundreds of circuits per second (securityweek.com).
- A key fix changes how relays' built-in DoS protections handle IPv6 traffic (gbhackers.com, securityweek.com).
- The attacker reportedly changes techniques during an attack. One operator said the attack changed form about ten minutes after their relay was upgraded to 0.4.9.17. The relay became unresponsive and lost HSDir status, and the attack stopped as soon as it lost that status (securityweek.com).
- That operator argues 0.4.9.17 does not do enough to protect HSDir relays (securityweek.com). This is a single operator's report and is not confirmed by the Tor Project.
- The release followed earlier releases: 0.4.9.16 on November 5 (gbhackers.com), and, per securityweek.com, less than three weeks after Tor 0.4.9.15, which introduced three DoS protections against a flood of directory requests.
Remediação
- Relay operators should upgrade to 0.4.9.17 immediately (tarballs are available from the Tor distribution site) and watch for follow-up releases (gbhackers.com, securityweek.com).
- Operators of HSDir relays should monitor for loss of HSDir status or unresponsiveness after upgrading, given the report above.
Relatos divergentes
- Deanonymization risk: gbhackers.com says the risk is to availability and performance, not anonymity, and mentions no deanonymization. securityweek.com relays an operator's warning that the attacker may be able to deanonymize and track onion services, and notes that the Tor Project has issued no such warning. The claim is unverified and contradicted by the project's silence on it.
- Verification: gbhackers.com says no independent confirmation from Tor's official channels was possible, and securityweek.com says its record is based on the article alone. Details are therefore secondary reporting.
Linha do tempo
-
Tor 0.4.9.17 Released as Ongoing DDoS Against Relays Continues, With Weak HSDir Protection Reported
ler a análise desta fonte ocultar
The Tor Project released Tor 0.4.9.17 on November 13 as a rapid response to an ongoing DDoS attack. The attack floods volunteer relays with client circuits and has affected most relay operators. The release patches several security issues. One of them concerns how the relays' built-in DoS protections handle IPv6. The project says more defenses are under consideration and that new versions should follow shortly. It urges relay operators to update without delay.
The release came less than three weeks after Tor 0.4.9.15. That version introduced three DoS protections against a flood of directory requests.
Relay operators report that the update has not ended the disruption. One operator said the attack changed form about ten minutes after their relay was upgraded. The relay became unresponsive and lost HSDir status. The operator argues that 0.4.9.17 does not do enough to protect HSDir relays. They also warn that the attacker may be able to deanonymize and track onion services. The Tor Project has issued no such warning.
Technical Details
- The attack is a flood of client circuits. A single relay can receive hundreds of circuits per second.
- The attacker reportedly changes techniques during an attack.
- The operator said the attack ceased as soon as the relay lost HSDir.
- The article gives no CVE, CVSS score or attribution for the attack.
Remediation
Relay operators should upgrade to Tor 0.4.9.17 immediately and watch for follow-up releases.
This record is based on the article alone. No web research was performed.
-
Tor Project releases 0.4.9.17 emergency update against ongoing DDoS circuit-flooding attack on relays
ler a análise desta fonte ocultar
The Tor Project released version 0.4.9.17 on November 13, 2026, announced by Network Team developer dgoulet, in response to an ongoing DDoS attack against relays on the Tor network. The attackers flood relays with client circuits, exhausting memory, CPU and bandwidth and causing slowdowns or disconnections. The release follows 0.4.9.16 of November 5, and Tor says more updates will come because a single patch cannot fully stop the flooding. The attackers and their motives have not been identified. Ordinary users need no action; the risk is to availability and performance, not anonymity, and no deanonymization is mentioned. No independent verification from Tor's official channels was possible during research.
Technical Details
The attack creates a very large number of circuits across the network. A key fix changes how relays handle IPv6 traffic as a defence against relay DoS.
Remediation
Relay operators should upgrade to 0.4.9.17 as soon as possible (tarballs from the Tor distribution site) and watch for follow-up releases.