CVE-2026-77639

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...

EUVD-2026-63648

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...

CVE-2026-77639

Tor before 0.4.9.9 is affected by a compression bomb bypass (TROVE-2026-022). An attacker can concatenate many gzip or zlib sub-streams , each individually just under the per-stream detection threshold, to circumvent the compression bomb check entirely. This results in a Denial of Service conditi...

CVE-2026-77639

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...

CVE-2026-77639

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...

EUVD-2026-63647

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...

CVE-2026-77638

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...

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.

CVE-2026-77638

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...

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...

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 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-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-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-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-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...