Torproject Tor vulnerabilities, page 3

48 vulnerabilities

Known vulnerabilities in Torproject Tor, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

9.3CVE-2026-77642debiantor+2
EPSS score
0.35%
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.
7.5CVE-2026-44602debiantor+2
EPSS score
0.60%
Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006.
7.5CVE-2026-44601debiantor+2
EPSS score
0.60%
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.
9.1CVE-2026-44597debiantor+2
EPSS score
0.63%
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.
5.3CVE-2026-44600debiantor+2
EPSS score
0.51%
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.
5.3CVE-2026-44599debiantor+2
EPSS score
0.40%
Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008.
9.1CVE-2026-44603debiantor+2
EPSS score
0.63%
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
6.5CVE-2023-23589debiantor+5
EPSS score
0.83%
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.