How severe is CVE-2020-8516?

CVE-2020-8516 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2020-8516 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (84th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-8516?

CVE-2020-8516 affects Torproject Tor. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-8516?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-8516 published?

CVE-2020-8516 was published on 2020-02-02 and last updated on 2026-06-17.

CVE-2020-8516

CVE-2020-8516 is a medium-severity vulnerability in Torproject Tor with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 5.3)
CVSS v2: 5.0
EPSS exploit prediction: 2% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Torproject Tor
Published: 2020-02-02
Last modified: 2026-06-17

Description

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 vulnerability

Frequently asked questions

What is CVE-2020-8516?: 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 vulnerability
How severe is CVE-2020-8516?: CVE-2020-8516 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2020-8516 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-8516?: CVE-2020-8516 affects Torproject Tor. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-8516?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-8516 published?: CVE-2020-8516 was published on 2020-02-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*

More vulnerabilities in Torproject Tor

CVE-2026-77638 — High (CVSS 8.9): Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could…
CVE-2026-77642 — High (CVSS 7.5): tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected…
CVE-2022-33903 — High (CVSS 7.5): Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation.
CVE-2021-38385 — High (CVSS 7.5): Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and…
CVE-2021-34550 — High (CVSS 7.5): An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006. The v3 onion service descriptor parsing allows…
CVE-2021-34549 — High (CVSS 7.5): An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain retrieval of…

All CVEs affecting Torproject Tor →