CVE Index中文
L4 · Septic Tank BlewTor · DDoS · IPv6tor-relay-ipv6-dos

Tor 0.4.9.17 strengthens IPv6 defenses during a relay DDoS attack

The Tor Project says a flood of client circuits affected most relay operators. Its emergency 0.4.9.17 release makes the relay's denial-of-service defenses count IPv6 clients by /64 prefix rather than by individual address.

Disclosed
Nov 13, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
Operators of Tor relays on older releases, especially relays receiving abusive client traffic over IPv6.
Tor · DDoS · IPv6
In the wild
Yes
Tor confirmed an ongoing relay DDoS and released an emergency mitigation.

What happened

During an ongoing distributed denial-of-service attack, a large volume of client circuits overloaded relays across the Tor network. The November release addresses a weakness in how the relay tracks IPv6 clients for its denial-of-service defenses. Before the change, the relay tracked each IPv6 address separately, so traffic from many addresses within one /64 received separate accounting. Version 0.4.9.17 groups that traffic by prefix. The Tor Project tracks the change as TROVE-2026-031. The announcement confirms the circuit flood and leaves open which techniques the attackers used.

The Tor Project was still evaluating further defenses when it published the release. In the same release, it removed the bastet directory authority’s keys over a possible compromise. The changelog does not confirm that those keys were compromised or link their removal to the circuit flood.

Fixed versions

ProductSafe fromNote
Tor0.4.9.17

Crime-scene timeline

  1. Oct 28, 2026

    Tor adds defenses against a flood of directory requests

    Tor 0.4.9.15 adds limits for BEGIN_DIR requests. The project warns that the limits do not stop the flood of circuit creation.

  2. Nov 13, 19:35 UTC

    Tor releases 0.4.9.17 while the attack continues

    The release groups IPv6 clients by /64 for DoS tracking. The Tor Project says most relay operators have been affected and that it is evaluating more defenses.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.