Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify reachable Tor node running pre-0.4.9.9
-
DeliveryCraft payload of concatenated gzip/zlib sub-streams each below detection threshold
-
ExploitTransmit stream to target node over network
-
ExecutionNode decompresses aggregate stream bypassing bomb check
-
PersistAggregate decompressed output exhausts node memory or CPU
-
ImpactDegrade node availability
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V13 - Configuration Unprotected alternate channel
|
| Exploitation Conditions | No special non-default configuration is required - any Tor node or relay running a version prior to 0.4.9.9 and accepting network connections is potentially vulnerable when processing compressed data streams. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms remote unauthenticated exploitation against default Tor deployments. Factors that limit exploitation: the availability impact is bounded at A:L (partial degradation, not full crash) because per-stream thresholds still constrain individual sub-stream expansion; network-level throughput limits cap the total decompressed volume an attacker can force in practice; and the attack affects only the processing node's resources rather than propagating across scope boundaries (S:U). Operators running high-bandwidth public relays or bridges that process large volumes of compressed data face the highest exposure. |
| Impact | The CVSS 5.3 Medium vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) indicates remote, unauthenticated, low-complexity exploitation with limited availability impact and no confidentiality or integrity consequences. The combination of PR:N and AC:L means the attack is trivially launchable without credentials or special conditions, which elevates practical risk above what a raw score of 5.3 might suggest. However, the A:L ceiling limits the worst-case impact to partial degradation rather than full denial of service. No EPSS data was provided in the input, so exploitation probability cannot be quantified from that signal - it is inferred as low given the absence of POC reports and KEV listing. The 'Authentication Bypass' tag in source metadata appears inconsistent with the actual mechanism (this is a detection evasion, not a traditional auth bypass); analysts should not conflate the two. Overall this is a real but moderate-priority issue: operators running public Tor nodes or relays face the most exposure, while private users have a reduced threat surface. |
| Exploit ScenarioDerived | An attacker crafts a specially constructed data stream composed of dozens or hundreds of concatenated gzip or zlib sub-streams, each sized deliberately just below Tor's per-sub-stream compression bomb threshold. This stream is submitted to a reachable Tor node over the network without any authentication; when the node decompresses the stream, the aggregate expanded output far exceeds what the per-stream check would have caught individually, consuming disproportionate memory or CPU. No POC has been identified at time of analysis, but the low-complexity CVSS vector suggests constructing such a payload requires only basic knowledge of the gzip/zlib container format. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 20, 2026
Compression bomb detection bypass in Tor before 0.4.9.9 enables remote unauthenticated attackers to deliver resource-exhausting payloads that evade the node's per-stream decompression safeguards. By concatenating multiple gzip or zlib sub-streams - each individually sized just below Tor's detection threshold - an attacker circumvents the aggregate bomb check entirely, potentially degrading availability of Tor nodes or relays. Tracked as TROVE-2026-022; no public exploit code or active exploitation (CISA KEV) has been identified; the CVSS 5.3 Medium score reflects the limited but real availability impact.
RemediationAI
The primary fix is to upgrade to Tor 0.4.9.9 or later, which resolves TROVE-2026-022 with multi-stream-aware compression bomb detection; the ChangeLog confirming the fix is at https://gitlab.torproject.org/tpo/core/tor/-/raw/tor-0.4.9.9/ChangeLog. For operators unable to patch immediately, a compensating control is to enforce strict rate limiting or connection throttling on inbound connections at the network perimeter, which constrains the volume of compressed data an attacker can deliver per time unit - note that this may reduce throughput for legitimate high-bandwidth Tor circuits. Disabling or restricting gzip/zlib compression negotiation entirely (if configurable for a given deployment role) would eliminate the attack surface at the cost of reduced bandwidth efficiency and interoperability with peers expecting compressed transport. No vendor workaround guidance beyond the upgrade was referenced in the available data.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Tor implements a compression bomb detection mechanism that inspects incoming gzip and zlib compressed data streams for excessively large expansion ratios, intended to prevent memory or CPU exhaustion from maliciously crafted payloads. The root cause (CWE-420: Unprotected Alternate Channel) is that the detection logic operates per sub-stream rather than on the aggregate decompressed output: an attacker exploits this by splitting a single logical bomb across many sub-streams, each one compliant with the per-stream threshold. The concatenated result bypasses the guard entirely while collectively expanding to a far larger payload than any individual sub-stream limit would suggest. Affected scope per CPE is cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:* - all Tor application versions prior to 0.4.9.9 across all platforms.
Know when Tor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Network-reachable unauthenticated attack with no special conditions; availability impact capped at Low as per-stream thresholds still bound individual sub-stream expansion.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
1DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Tor Browser before 7.0.9 on macOS and Linux allows remote attackers to bypass the intended anonymity feature and discove
Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-s
A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. Rated high severity (CVSS 7.5), this vulnerability
The SafeSocks option in Tor before 0.4.7.13 has a logic error in which the unsafe SOCKS4 protocol can be used but not th
Out-of-bounds write in The Tor Project's tor daemon (0.2.8.2-alpha through versions before 0.4.9.9) can be triggered whe
The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before att
Rendezvous-point impersonation in Tor before 0.4.9.11 lets a malicious relay that a client happens to select as its rend
Write-after-free in Tor's conflux (traffic-splitting) subsystem allows a remote unauthenticated attacker to crash a Tor
Use-after-free in Tor's conflux circuit handling allows a malicious Tor client to corrupt relay memory by sending a RELA
In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and 0.3.1 bef
Tor before 0.2.8.12 might allow remote attackers to cause a denial of service (client crash) via a crafted hidden servic
Tor before 0.2.8.9 and 0.2.9.x before 0.2.9.4-alpha had internal functions that were entitled to expect that buf_t data
EUVD-2026-63648
GHSA-jm5p-g55h-rwhg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB