cbcvebase.

Torproject Tor vulnerabilities

100 known vulnerabilities affecting torproject/tor.

Total CVEs
100
CISA KEV
0
Public exploits
2
Exploited in wild
0
Severity breakdown
CRITICAL6HIGH31MEDIUM61LOW2

Vulnerabilities

Page 1 of 5
CVE-2018-0491P3HIGHCVSS 7.5PoC≥ 0.3.2.0, < 0.3.2.10vTor2018-03-05
CVE-2018-0491 [HIGH] CWE-416 CVE-2018-0491: A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. It allows remote attackers to A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. It allows remote attackers to cause a denial of service (relay crash) because the KIST implementation allows a channel to be added more than once in the pending list.
nvdosv
CVE-2007-4174P3MEDIUMCVSS 5.8PoC≥ 0, < 0.1.2.16-12007-08-07
CVE-2007-4174 [MEDIUM] CVE-2007-4174: Tor before 0 Tor before 0.1.2.16, when ControlPort is enabled, does not properly restrict commands to localhost port 9051, which allows remote attackers to modify the torrc configuration file, compromise anonymity, and have other unspecified impact via HTTP POST data containing commands without valid authentication, as demonstrated by an HTML form (1) hosted on a web site or (2) injected by a Tor exit node.
osv
CVE-2010-1676P3CRITICALCVSS 10.0≥ 0, < 0.2.1.26-62010-12-22
CVE-2010-1676 [CRITICAL] CVE-2010-1676: Heap-based buffer overflow in Tor before 0 Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via unspecified vectors.
osv
CVE-2026-44603P3CRITICALCVSS 9.1fixed in 0.4.9.72026-05-07
CVE-2026-44603 [CRITICAL] CWE-193 CVE-2026-44603: Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026- Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
nvd
CVE-2026-44597P3CRITICALCVSS 9.1fixed in 0.4.9.72026-05-07
CVE-2026-44597 [CRITICAL] CWE-684 CVE-2026-44597: Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a re Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in its payload, aka TROVE-2026-011.
nvd
CVE-2017-0377P3HIGHCVSS 7.5v0.3.0.1v0.3.0.2+7 more2017-07-02
CVE-2017-0377 [HIGH] CWE-200 CVE-2017-0377: Tor 0.3.x before 0.3.0.9 has a guard-selection algorithm that only considers the exit relay (not the Tor 0.3.x before 0.3.0.9 has a guard-selection algorithm that only considers the exit relay (not the exit relay's family), which might allow remote attackers to defeat intended anonymity properties by leveraging the existence of large families.
nvd
CVE-2021-34548P3HIGHCVSS 7.5fixed in 0.3.5.15≥ 0.4.0.0, < 0.4.4.9+2 more2021-06-29
CVE-2021-34548 [HIGH] CWE-290 CVE-2021-34548: An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-003. An attacker can forge RELAY_END o An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-003. An attacker can forge RELAY_END or RELAY_RESOLVED to bypass the intended access control for ending a stream.
nvdosv
CVE-2021-28089P3HIGHCVSS 7.5fixed in 0.3.5.14≥ 0.4.4.4, < 0.4.4.8+5 more2021-03-19
CVE-2021-28089 [HIGH] CWE-400 CVE-2021-28089: Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resource Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resources on a target, aka TROVE-2021-001.
nvdosv
CVE-2017-11565P3HIGHCVSS 7.5≥ 0, < 0.3.1.7-12017-07-23
CVE-2017-11565 [HIGH] CVE-2017-11565: debian/tor debian/tor.init in the Debian tor_0.2.9.11-1~deb9u1 package for Tor was designed to execute aa-exec from the standard system pathname if the apparmor package is installed, but implements this incorrectly (with a wrong assumption that the specific pathname would remain the same forever), which allows attackers to bypass intended AppArmor restrictions by leveraging the silent loss of this protection mechanism. NOTE: this does not affect systems, suc
osv
CVE-2026-44601P3HIGHCVSS 7.5fixed in 0.4.9.72026-05-07
CVE-2026-44601 [HIGH] CWE-837 CVE-2026-44601: Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a double close of a circuit, aka TROVE-2026-009.
nvd
CVE-2011-2778P3HIGHCVSS 7.6≥ 0, < 0.2.2.35-12011-12-23
CVE-2011-2778 [HIGH] CVE-2011-2778: Multiple heap-based buffer overflows in Tor before 0 Multiple heap-based buffer overflows in Tor before 0.2.2.35 allow remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code by (1) establishing a SOCKS connection to SocksPort or (2) leveraging a SOCKS proxy configuration.
osv
CVE-2017-8823P3HIGHCVSS 8.1≥ 0, < 0.3.1.9-12017-12-03
CVE-2017-8823 [HIGH] CVE-2017-8823: In Tor before 0 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 before 0.3.1.9, there is a use-after-free in onion service v2 during intro-point expiration because the expiring list is mismanaged in certain error cases, aka TROVE-2017-013.
osv
CVE-2008-5398P3CRITICALCVSS 9.3≥ 0, < 0.2.0.32-12008-12-09
CVE-2008-5398 [CRITICAL] CVE-2008-5398: Tor before 0 Tor before 0.2.0.32 does not properly process the ClientDNSRejectInternalAddresses configuration option in situations where an exit relay issues a policy-based refusal of a stream, which allows remote exit relays to have an unknown impact by mapping an internal IP address to the destination hostname of a refused stream.
osv
CVE-2015-2689P3HIGHCVSS 7.5fixed in 0.2.4.26≥ 0.2.5.1, < 0.2.5.112020-01-24
CVE-2015-2689 [HIGH] CWE-20 CVE-2015-2689: Tor before 0.2.4.26 and 0.2.5.x before 0.2.5.11 does not properly handle pending-connection resolve Tor before 0.2.4.26 and 0.2.5.x before 0.2.5.11 does not properly handle pending-connection resolve states during periods of high DNS load, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via crafted packets.
nvdosv
CVE-2016-8860P3HIGHCVSS 7.5≤ 0.2.8.8v0.2.9.0+3 more2017-01-04
CVE-2016-8860 [HIGH] CWE-119 CVE-2016-8860: Tor before 0.2.8.9 and 0.2.9.x before 0.2.9.4-alpha had internal functions that were entitled to exp 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 had NUL termination, but the implementation of or/buffers.c did not ensure that NUL termination was present, which allows remote attackers to cause a denial of service (client, hidden service, relay, or authority crash) via crafted dat
nvdosv
CVE-2021-38385P3HIGHCVSS 7.5fixed in 0.3.5.16≥ 0.4.0.0, < 0.4.5.10+1 more2021-08-30
CVE-2021-38385 [HIGH] CWE-617 CVE-2021-38385: Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verif Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007.
nvdosv
CVE-2021-34549P3HIGHCVSS 7.5fixed in 0.3.5.15≥ 0.4.0.0, < 0.4.4.9+2 more2021-06-29
CVE-2021-34549 [HIGH] CWE-400 CVE-2021-34549: An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain retrieval of circuit data. Consequently. an attacker can trigger the use of an attacker-chosen circuit ID to cause algorithm inefficiency.
nvdosv
CVE-2021-34550P3HIGHCVSS 7.5fixed in 0.3.5.15≥ 0.4.0.0, < 0.4.4.9+2 more2021-06-29
CVE-2021-34550 [HIGH] CWE-119 CVE-2021-34550: An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006. The v3 onion service descriptor p An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006. The v3 onion service descriptor parsing allows out-of-bounds memory access, and a client crash, via a crafted onion service descriptor
nvdosv
CVE-2020-15572P3HIGHCVSS 7.5fixed in 0.3.5.11fixed in 0.4.2.8+3 more2020-07-15
CVE-2020-15572 [HIGH] CWE-125 CVE-2020-15572: Tor before 0.4.3.6 has an out-of-bounds memory access that allows a remote denial-of-service (crash) Tor before 0.4.3.6 has an out-of-bounds memory access that allows a remote denial-of-service (crash) attack against Tor instances built to use Mozilla Network Security Services (NSS), aka TROVE-2020-001.
nvdosv
CVE-2026-44602P3HIGHCVSS 7.5fixed in 0.4.9.72026-05-07
CVE-2026-44602 [HIGH] CWE-476 CVE-2026-44602: Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TRO Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006.
nvd
Torproject Tor vulnerabilities | cvebase