← Back

Torproject

torproject

46 CVEs • 2 products

Products (2)

Click to collapse
Toggle
Tor
tor
Tor Browser
tor_browser

CVEs (46)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
9.1 CRITICAL· v3
N/A· v2
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
7.5 HIGH· v3
N/A· v2
Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006.
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
7.5 HIGH· v3
N/A· v2
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.
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka TROVE-2026-010.
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008.
1Torproject
1Tor
Jun 17, 2026
May 7, 2026
N/A· v4
9.1 CRITICAL· v3
N/A· v2
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.
3Debian
FedoraprojectTorproject
3Debian Linux
FedoraTor
Jun 17, 2026
Jan 14, 2023
N/A· v4
6.5 MEDIUM· v3
N/A· v2
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 the safe SOCKS4a protocol, aka TROVE-2022-002.
1Torproject
1Tor
Jun 17, 2026
Jul 17, 2022
N/A· v4
7.5 HIGH· v3
N/A· v2
Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation.
1Torproject
1Tor
Jun 17, 2026
Feb 26, 2022
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
Tor Browser 9.0.7 on Windows 10 build 10586 is vulnerable to information disclosure. This could allow local attackers to bypass the intended anonymity feature and obtain information regarding the onion services visited b...Show more
Tor Browser 9.0.7 on Windows 10 build 10586 is vulnerable to information disclosure. This could allow local attackers to bypass the intended anonymity feature and obtain information regarding the onion services visited by a local user. This can be accomplished by analyzing RAM memory even several hours after the local user used the product. This occurs because the product doesn't properly free memory.Show less
1Torproject
1Tor Browser
Jun 17, 2026
Sep 24, 2021
N/A· v4
6.1 MEDIUM· v3
3.6 LOW· v2
Tor Browser through 10.5.6 and 11.x through 11.0a4 allows a correlation attack that can compromise the privacy of visits to v2 onion addresses. Exact timestamps of these onion-service visits are logged locally, and an at...Show more
Tor Browser through 10.5.6 and 11.x through 11.0a4 allows a correlation attack that can compromise the privacy of visits to v2 onion addresses. Exact timestamps of these onion-service visits are logged locally, and an attacker might be able to compare them to timestamp data collected by the destination server (or collected by a rogue site within the Tor network).Show less
1Torproject
1Tor
Jun 17, 2026
Aug 30, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
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.
1Torproject
1Tor
Jun 17, 2026
Jun 29, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
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
1Torproject
1Tor
Jun 17, 2026
Jun 29, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
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 algo...Show more
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.Show less
1Torproject
1Tor
Jun 17, 2026
Jun 29, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
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.
2Fedoraproject
Torproject
2Fedora
Tor
Jun 17, 2026
Mar 19, 2021
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
Tor before 0.4.5.7 allows a remote attacker to cause Tor directory authorities to exit with an assertion failure, aka TROVE-2021-002.
2Fedoraproject
Torproject
2Fedora
Tor
Jun 17, 2026
Mar 19, 2021
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
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.
1Torproject
1Tor
Jun 17, 2026
Jul 15, 2020
N/A· v4
7.5 HIGH· v3
4.3 MEDIUM· v2
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.
2Opensuse
Torproject
3Backports Sle
LeapTor
Jun 17, 2026
Mar 23, 2020
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), aka TROVE-2020-004. This occurs in circpad_setup_machine_on_circ because a circuit...Show more
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), aka TROVE-2020-004. This occurs in circpad_setup_machine_on_circ because a circuit-padding machine can be negotiated twice on the same circuit.Show less
2Opensuse
Torproject
3Backports
LeapTor
Jun 17, 2026
Mar 23, 2020
N/A· v4
7.5 HIGH· v3
7.8 HIGH· v2
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (CPU consumption), aka TROVE-2020-002.
1Torproject
1Tor
Jun 17, 2026
Feb 2, 2020
N/A· v4
5.3 MEDIUM· v3
5.0 MEDIUM· v2
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 attempting to connect to it, which might make it easier for remote attackers to discover circuit inform...Show more
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 attempting to connect to it, which might make it easier for remote attackers to discover circuit information. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerabilityShow less