https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2012-3519.htmlhttps://patchthecve.com/cve/CVE-2012-3519.htmlTue, 16 Jun 2026 23:43:23 +0000MEDIUM 5.0: routerlist.c in Tor before 0.2.2.38 uses a different amount of time for relay-list iteration depending on which relay is chosen, which might allow remote attackers to obtain sensitive information about relay selection via a timing side-channel attack.https://patchthecve.com/cve/CVE-2012-3518.htmlhttps://patchthecve.com/cve/CVE-2012-3518.htmlTue, 16 Jun 2026 23:43:23 +0000MEDIUM 5.0: The networkstatus_parse_vote_from_string function in routerparse.c in Tor before 0.2.2.38 does not properly handle an invalid flavor name, which allows remote attackers to cause a denial of service (out-of-bounds read and daemon crash) via a crafted (1) vote document or (2) consensus document.https://patchthecve.com/cve/CVE-2012-3517.htmlhttps://patchthecve.com/cve/CVE-2012-3517.htmlTue, 16 Jun 2026 23:43:23 +0000MEDIUM 5.0: Use-after-free vulnerability in dns.c in Tor before 0.2.2.38 might allow remote attackers to cause a denial of service (daemon crash) via vectors related to failed DNS requests.https://patchthecve.com/cve/CVE-2011-4897.htmlhttps://patchthecve.com/cve/CVE-2011-4897.htmlTue, 16 Jun 2026 23:35:35 +0000MEDIUM 4.3: Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.https://patchthecve.com/cve/CVE-2011-4896.htmlhttps://patchthecve.com/cve/CVE-2011-4896.htmlTue, 16 Jun 2026 23:35:35 +0000MEDIUM 4.3: Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might allow remote attackers to obtain sensitive information about clients in opportunistic circumstances by monitoring network traffic to the bridge port.https://patchthecve.com/cve/CVE-2011-4895.htmlhttps://patchthecve.com/cve/CVE-2011-4895.htmlTue, 16 Jun 2026 23:35:35 +0000MEDIUM 4.3: Tor before 0.2.2.34, when configured as a bridge, sets up circuits through a process different from the process used by a client, which makes it easier for remote attackers to enumerate bridges by observing circuit building.https://patchthecve.com/cve/CVE-2011-4894.htmlhttps://patchthecve.com/cve/CVE-2011-4894.htmlTue, 16 Jun 2026 23:35:34 +0000MEDIUM 4.3: Tor before 0.2.2.34, when configured as a bridge, uses direct DirPort access instead of a Tor TLS connection for a directory fetch, which makes it easier for remote attackers to enumerate bridges by observing DirPort connections.https://patchthecve.com/cve/CVE-2011-2778.htmlhttps://patchthecve.com/cve/CVE-2011-2778.htmlTue, 16 Jun 2026 23:31:59 +0000HIGH 7.6: 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.https://patchthecve.com/cve/CVE-2011-2769.htmlhttps://patchthecve.com/cve/CVE-2011-2769.htmlTue, 16 Jun 2026 23:31:58 +0000MEDIUM 4.3: Tor before 0.2.2.34, when configured as a bridge, accepts the CREATE and CREATE_FAST values in the Command field of a cell within an OR connection that it initiated, which allows remote relays to enumerate bridges by using these values.https://patchthecve.com/cve/CVE-2011-2768.htmlhttps://patchthecve.com/cve/CVE-2011-2768.htmlTue, 16 Jun 2026 23:31:57 +0000MEDIUM 5.8: Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selectedhttps://patchthecve.com/cve/CVE-2011-1924.htmlhttps://patchthecve.com/cve/CVE-2011-1924.htmlTue, 16 Jun 2026 23:30:22 +0000MEDIUM 5.0: Buffer overflow in the policy_summarize function in or/policies.c in Tor before 0.2.1.30 allows remote attackers to cause a denial of service (directory authority crash) via a crafted policy that triggers creation of a long port list.https://patchthecve.com/cve/CVE-2011-0493.htmlhttps://patchthecve.com/cve/CVE-2011-0493.htmlTue, 16 Jun 2026 23:27:30 +0000MEDIUM 5.0: Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors related to malformed router caches and improper handling of integer values.https://patchthecve.com/cve/CVE-2011-0492.htmlhttps://patchthecve.com/cve/CVE-2011-0492.htmlTue, 16 Jun 2026 23:27:29 +0000MEDIUM 5.0: Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha allows remote attackers to cause a denial of service (assertion failure and daemon exit) via blobs that trigger a certain file size, as demonstrated by the cached-descriptors.new file.https://patchthecve.com/cve/CVE-2011-0491.htmlhttps://patchthecve.com/cve/CVE-2011-0491.htmlTue, 16 Jun 2026 23:27:29 +0000MEDIUM 5.0: The tor_realloc function in Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not validate a certain size value during memory allocation, which might allow remote attackers to cause a denial of service (daemon crash) via unspecified vectors, related to "underflow errors."https://patchthecve.com/cve/CVE-2011-0490.htmlhttps://patchthecve.com/cve/CVE-2011-0490.htmlTue, 16 Jun 2026 23:27:29 +0000MEDIUM 5.0: Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha makes calls to Libevent within Libevent log handlers, which might allow remote attackers to cause a denial of service (daemon crash) via vectors that trigger certain log messages.https://patchthecve.com/cve/CVE-2011-0427.htmlhttps://patchthecve.com/cve/CVE-2011-0427.htmlTue, 16 Jun 2026 23:27:20 +0000MEDIUM 6.8: Heap-based buffer overflow in Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors.https://patchthecve.com/cve/CVE-2011-0016.htmlhttps://patchthecve.com/cve/CVE-2011-0016.htmlTue, 16 Jun 2026 23:26:37 +0000LOW 2.1: Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly manage key data in memory, which might allow local users to obtain sensitive information by leveraging the ability to read memory that was previously used by a different process.https://patchthecve.com/cve/CVE-2011-0015.htmlhttps://patchthecve.com/cve/CVE-2011-0015.htmlTue, 16 Jun 2026 23:26:37 +0000MEDIUM 5.0: Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly check the amount of compression in zlib-compressed data, which allows remote attackers to cause a denial of service via a large compression factor.https://patchthecve.com/cve/CVE-2010-1676.htmlhttps://patchthecve.com/cve/CVE-2010-1676.htmlTue, 16 Jun 2026 23:19:05 +0000HIGH 10.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.https://patchthecve.com/cve/CVE-2010-0385.htmlhttps://patchthecve.com/cve/CVE-2010-0385.htmlTue, 16 Jun 2026 23:16:03 +0000MEDIUM 5.0: Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, when functioning as a bridge directory authority, allows remote attackers to obtain sensitive information about bridge identities and bridge descriptors via a dbg-stability.txt directory query.https://patchthecve.com/cve/CVE-2010-0384.htmlhttps://patchthecve.com/cve/CVE-2010-0384.htmlTue, 16 Jun 2026 23:16:03 +0000LOW 2.1: Tor 0.2.2.x before 0.2.2.7-alpha, when functioning as a directory mirror, does not prevent logging of the client IP address upon detection of erroneous client behavior, which might make it easier for local users to discover the identities of clients in opportunistic circumstances by reading log filehttps://patchthecve.com/cve/CVE-2010-0383.htmlhttps://patchthecve.com/cve/CVE-2010-0383.htmlTue, 16 Jun 2026 23:16:03 +0000MEDIUM 5.0: Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity keys for certain directory authorities, which makes it easier for man-in-the-middle attackers to compromise the anonymity of traffic sources and destinations.https://patchthecve.com/cve/CVE-2009-2426.htmlhttps://patchthecve.com/cve/CVE-2009-2426.htmlTue, 16 Jun 2026 23:09:25 +0000MEDIUM 5.0: The connection_edge_process_relay_cell_not_open function in src/or/relay.c in Tor 0.2.x before 0.2.0.35 and 0.1.x before 0.1.2.8-beta allows exit relays to have an unspecified impact by causing controllers to accept DNS responses that redirect to an internal IP address via unknown vectors. NOTE: sohttps://patchthecve.com/cve/CVE-2009-2425.htmlhttps://patchthecve.com/cve/CVE-2009-2425.htmlTue, 16 Jun 2026 23:09:25 +0000MEDIUM 5.0: Tor before 0.2.0.35 allows remote attackers to cause a denial of service (application crash) via a malformed router descriptor.https://patchthecve.com/cve/CVE-2009-0939.htmlhttps://patchthecve.com/cve/CVE-2009-0939.htmlTue, 16 Jun 2026 23:06:09 +0000HIGH 10.0: Tor before 0.2.0.34 treats incomplete IPv4 addresses as valid, which has unknown impact and attack vectors related to "Spec conformance," as demonstrated using 192.168.0.https://patchthecve.com/cve/CVE-2009-0938.htmlhttps://patchthecve.com/cve/CVE-2009-0938.htmlTue, 16 Jun 2026 23:06:09 +0000MEDIUM 5.0: Unspecified vulnerability in Tor before 0.2.0.34 allows directory mirrors to cause a denial of service (exit node crash) via "malformed input."https://patchthecve.com/cve/CVE-2009-0937.htmlhttps://patchthecve.com/cve/CVE-2009-0937.htmlTue, 16 Jun 2026 23:06:08 +0000MEDIUM 5.0: Unspecified vulnerability in Tor before 0.2.0.34 allows directory mirrors to cause a denial of service via unknown vectors.https://patchthecve.com/cve/CVE-2009-0936.htmlhttps://patchthecve.com/cve/CVE-2009-0936.htmlTue, 16 Jun 2026 23:06:08 +0000MEDIUM 5.0: Unspecified vulnerability in Tor before 0.2.0.34 allows attackers to cause a denial of service (infinite loop) via "corrupt votes."https://patchthecve.com/cve/CVE-2009-0654.htmlhttps://patchthecve.com/cve/CVE-2009-0654.htmlTue, 16 Jun 2026 23:05:30 +0000MEDIUM 5.1: Tor 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router and an exit router, to confirm that a sender and receiver are communicating via vectors involving (1) replaying, (2) modifying, (3) inserting, or (4) deleting a single cell, and then observing chttps://patchthecve.com/cve/CVE-2009-0414.htmlhttps://patchthecve.com/cve/CVE-2009-0414.htmlTue, 16 Jun 2026 23:04:59 +0000HIGH 10.0: Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption.https://patchthecve.com/cve/CVE-2008-5398.htmlhttps://patchthecve.com/cve/CVE-2008-5398.htmlTue, 16 Jun 2026 22:59:53 +0000HIGH 9.3: 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 hostnamehttps://patchthecve.com/cve/CVE-2008-5397.htmlhttps://patchthecve.com/cve/CVE-2008-5397.htmlTue, 16 Jun 2026 22:59:53 +0000HIGH 7.2: Tor before 0.2.0.32 does not properly process the (1) User and (2) Group configuration options, which might allow local users to gain privileges by leveraging unintended supplementary group memberships of the Tor process.https://patchthecve.com/cve/CVE-2007-4174.htmlhttps://patchthecve.com/cve/CVE-2007-4174.htmlTue, 16 Jun 2026 22:43:32 +0000MEDIUM 5.8: 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 authenticathttps://patchthecve.com/cve/CVE-2007-4099.htmlhttps://patchthecve.com/cve/CVE-2007-4099.htmlTue, 16 Jun 2026 22:43:23 +0000MEDIUM 5.8: Tor before 0.1.2.15 can select a guard node beyond the first listed never-before-connected-to guard node, which allows remote attackers with control of certain guard nodes to obtain sensitive information and possibly leverage further attacks.https://patchthecve.com/cve/CVE-2007-4098.htmlhttps://patchthecve.com/cve/CVE-2007-4098.htmlTue, 16 Jun 2026 22:43:23 +0000MEDIUM 5.8: Tor before 0.1.2.15 does not properly distinguish "streamids from different exits," which might allow remote attackers with control over Tor routers to inject cells into arbitrary streams.https://patchthecve.com/cve/CVE-2007-4097.htmlhttps://patchthecve.com/cve/CVE-2007-4097.htmlTue, 16 Jun 2026 22:43:23 +0000MEDIUM 6.4: Tor before 0.1.2.15 sends "destroy cells" containing the reason for tearing down a circuit, which allows remote attackers to obtain sensitive information, contrary to specifications.https://patchthecve.com/cve/CVE-2007-4096.htmlhttps://patchthecve.com/cve/CVE-2007-4096.htmlTue, 16 Jun 2026 22:43:23 +0000MEDIUM 5.8: Buffer overflow in Tor before 0.1.2.15, when using BSD natd support, allows remote attackers to cause a denial of service via unspecified vectors.https://patchthecve.com/cve/CVE-2007-3165.htmlhttps://patchthecve.com/cve/CVE-2007-3165.htmlTue, 16 Jun 2026 22:41:11 +0000MEDIUM 5.0: Tor before 0.1.2.14 can construct circuits in which an entry guard is in the same family as the exit node, which might compromise the anonymity of traffic sources and destinations by exposing traffic to inappropriate remote observers.https://patchthecve.com/cve/CVE-2007-1103.htmlhttps://patchthecve.com/cve/CVE-2007-1103.htmlTue, 16 Jun 2026 22:36:57 +0000MEDIUM 4.3: Tor does not verify a node's uptime and bandwidth advertisements, which allows remote attackers who operate a low resource node to make false claims of greater resources, which places the node into use for many circuits and compromises the anonymity of traffic sources and destinations.https://patchthecve.com/cve/CVE-2006-6893.htmlhttps://patchthecve.com/cve/CVE-2006-6893.htmlTue, 16 Jun 2026 22:34:00 +0000MEDIUM 5.0: Tor allows remote attackers to discover the IP address of a hidden service by accessing this service at a high rate, thereby changing the server's CPU temperature and consequently changing the pattern of time values visible through (1) ICMP timestamps, (2) TCP sequence numbers, and (3) TCP timestamphttps://patchthecve.com/cve/CVE-2006-4508.htmlhttps://patchthecve.com/cve/CVE-2006-4508.htmlTue, 16 Jun 2026 22:29:14 +0000MEDIUM 4.0: Unspecified vulnerability in (1) Tor 0.1.0.x before 0.1.0.18 and 0.1.1.x before 0.1.1.23, and (2) ScatterChat before 1.0.2, allows remote attackers operating a Tor entry node to route arbitrary Tor traffic through clients or cause a denial of service (flood) via unspecified vectors.https://patchthecve.com/cve/CVE-2006-3419.htmlhttps://patchthecve.com/cve/CVE-2006-3419.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 5.0: Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically strong RAND_bytes, and seeds the entropy value at start-up with 160-bit chunks without reseeding, which makes it easier for attackers to conduct brute force guessing attacks.https://patchthecve.com/cve/CVE-2006-3418.htmlhttps://patchthecve.com/cve/CVE-2006-3418.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 5.0: Tor before 0.1.1.20 does not validate that a server descriptor's fingerprint line matches its identity key, which allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications.https://patchthecve.com/cve/CVE-2006-3417.htmlhttps://patchthecve.com/cve/CVE-2006-3417.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 6.4: Tor client before 0.1.1.20 prefers entry points based on is_fast or is_stable flags, which could allow remote attackers to be preferred over nodes that are identified as more trustworthy "entry guard" (is_guard) systems by directory authorities.https://patchthecve.com/cve/CVE-2006-3416.htmlhttps://patchthecve.com/cve/CVE-2006-3416.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 5.0: Tor before 0.1.1.20 kills the circuit when it receives an unrecognized relay command, which causes network circuits to be disbanded. NOTE: while this item is listed under the "Security fixes" section of the developer changelog, the developer clarified on 20060707 that this is only a self-DoS. Therhttps://patchthecve.com/cve/CVE-2006-3415.htmlhttps://patchthecve.com/cve/CVE-2006-3415.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 6.4: Tor before 0.1.1.20 uses improper logic to validate the "OR" destination, which allows remote attackers to perform a man-in-the-middle (MITM) attack via unspecified vectors.https://patchthecve.com/cve/CVE-2006-3414.htmlhttps://patchthecve.com/cve/CVE-2006-3414.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 5.0: Tor before 0.1.1.20 supports server descriptors that contain hostnames instead of IP addresses, which allows remote attackers to arbitrarily group users by providing preferential address resolution.https://patchthecve.com/cve/CVE-2006-3413.htmlhttps://patchthecve.com/cve/CVE-2006-3413.htmlTue, 16 Jun 2026 22:27:01 +0000MEDIUM 5.0: The privoxy configuration file in Tor before 0.1.1.20, when run on Apple OS X, logs all data via the "logfile", which allows attackers to obtain potentially sensitive information.https://patchthecve.com/cve/CVE-2006-3412.htmlhttps://patchthecve.com/cve/CVE-2006-3412.htmlTue, 16 Jun 2026 22:27:00 +0000MEDIUM 6.4: Tor before 0.1.1.20 does not sufficiently obey certain firewall options, which allows remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers.https://patchthecve.com/cve/CVE-2006-3411.htmlhttps://patchthecve.com/cve/CVE-2006-3411.htmlTue, 16 Jun 2026 22:27:00 +0000MEDIUM 6.4: TLS handshakes in Tor before 0.1.1.20 generate public-private keys based on TLS context rather than the connection, which makes it easier for remote attackers to conduct brute force attacks on the encryption keys.