CVE-2026-77638

Tor before 0.4.9.11 has a rendezvous-point race condition allowing a relay to impersonate an onion service and intercept client traffic, yielding HIGH confidentiality/integrity impact (CVSS 8.9). No in-the-wild exploitation is documented; upgrade to 0.4.9.11 to remediate.

EUVD-2026-63593

Tor before 0.4.9.11 is prone to a use-after-free and potential double free of a conflux object when a recovery leg revives a conflux set whose last linked leg has already been closed. A malicious exit node could use this to crash a client. This is TROVE-2026-026...

CVE-2026-77587

Tor versions before 0.4.9.11 are affected by a use-after-free (and potential double free ) vulnerability in the handling of conflux objects . The root cause occurs when a recovery leg revives a conflux set whose last linked leg has already been closed, leaving a dangling pointer. A malicious exit...

CVE-2026-77587

Tor before 0.4.9.11 is prone to a use-after-free and potential double free of a conflux object when a recovery leg revives a conflux set whose last linked leg has already been closed. A malicious exit node could use this to crash a client. This is TROVE-2026-026...

CVE-2026-77584

Tor before 0.4.9.10 fails to reject a CONFLUX_LINK cell on a circuit with attached streams; a malicious client sends RELAY_COMMAND_BEGIN first, orphaning an exit stream that leaves a dangling circuit back-pointer and triggers use-after-free when the circuit is freed. CVSS 3.1 scores 7.0 (HIGH). F...

CVE-2026-77584

Tor before 0.4.9.10 did not reject a CONFLUXLINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAYCOMMANDBEGIN before the CONFLUXLINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit...

EUVD-2026-63591

Tor before 0.4.9.10 did not reject a CONFLUXLINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAYCOMMANDBEGIN before the CONFLUXLINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit...

CVE-2026-77584

Tor before 0.4.9.10 did not reject a CONFLUXLINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAYCOMMANDBEGIN before the CONFLUXLINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit...

PT-2026-79150

tor before 0.4.9.9 was prone to an infinite loop when decompressing a truncated zlib/gzip stream with done=1. A truncated stream never reaches Z STREAM END, causing zlib to return Z BUF ERROR with no input remaining, which buf add compress mistook for a full output buffer and retried forever. Fix...

PT-2026-79149

Tor before 0.4.9.9 was prone to a compression bomb bypass where an attacker could concatenate many gzip or zlib sub-streams, each just under the per-stream detection threshold, to avoid the compression bomb check entirely. This is TROVE-2026-022...

PT-2026-79219

tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest type. Impact is minor for most Tor roles, but potentially major for directory authorities. This is TROVE-2026-019...

PT-2026-79132

Tor before 0.4.9.10 did not reject a CONFLUX LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAY COMMAND BEGIN before the CONFLUX LINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit...

PT-2026-79133

Tor before 0.4.9.11 is prone to a use-after-free and potential double free of a conflux object when a recovery leg revives a conflux set whose last linked leg has already been closed. A malicious exit node could use this to crash a client. This is TROVE-2026-026...

PT-2026-79151

tor before 0.4.9.9 was prone to a NULL write after free when sending a CONFLUX SWITCH cell fails. The return value of relay send command from edge was ignored, so a send failure which calls circuit mark for close and removes the leg via cfx del leg would go undetected, causing the caller to write...

PT-2026-79148

Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle impersonate the onion service that the client was trying to reach...

GHSA-XPMJ-WJCP-6PWW

creationtimestamp| type| source ---|---|--- 2026-08-19 09:32:00+00:00| seen| https://gist.github.com/alon710/f8eaee2020ed8f819add6f9d1de77bf8...

Kimwolf v7 Android Botnet Makes HTTP/2 DDoS Traffic Look Like Legitimate Browsing

Cybersecurity researchers have discovered a new version of the Kimwolf/AISURU Android and Internet of Things IoT botnet that comes with significant improvements to improve its operational resilience and conduct distributed denial-of-service DDoS attacks. The new version, tracked as Kimwolf v7, wa...

CVE-2026-48098

NexTor IP Changer is a command-line tool that leverages the Tor network to periodically rotate a user's IP address. Versions prior to 2.0.0 execute privileged system commands using sudo and shell=True directly inside application logic. In environments where passwordless sudo NOPASSWD is enabled,...

EUVD-2026-54604

NexTor IP Changer is a command-line tool that leverages the Tor network to periodically rotate a user's IP address. Versions prior to 2.0.0 execute privileged system commands using sudo and shell=True directly inside application logic. In environments where passwordless sudo NOPASSWD is enabled,...

CVE-2026-48098 NexTOR IP Changer Unsafely Uses sudo and shell=True

NexTor IP Changer is a command-line tool that leverages the Tor network to periodically rotate a user's IP address. Versions prior to 2.0.0 execute privileged system commands using sudo and shell=True directly inside application logic. In environments where passwordless sudo NOPASSWD is enabled,...