Skip to main content

Tor CVE-2026-77587

| EUVDEUVD-2026-63593 MEDIUM
Improper Update of Reference Count (CWE-911)
2026-08-20 mitre GHSA-9mf5-x83c-fg2x
5.9
CVSS 3.1 · Vendor: mitre
Share

Severity by source

Vendor (mitre) PRIMARY
5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.9 MEDIUM

Exit-node position and precise timing requirement justify AC:H; pure crash impact with no confidentiality or integrity effect yields C:N/I:N/A:H.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Analysis Generated
Aug 20, 2026 - 21:40 vuln.today
Patch available
Aug 20, 2026 - 21:18 EUVD

DescriptionCVE.org

Tor before 0.4.9.11 is prone to a use-after-free (and potential double free) of a conflux object when a recovery leg revives a conflux set whose last linked leg has already been closed. A malicious exit node could use this to crash a client. This is TROVE-2026-026.

AnalysisAI

Use-after-free and potential double-free in Tor's conflux subsystem before version 0.4.9.11 enables a malicious exit node to crash Tor clients by triggering memory corruption during circuit recovery. The defect activates when a recovery leg attempts to revive a conflux set whose last linked leg has already been deallocated, resulting in access to freed memory and a possible second free of the same object. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Operate malicious Tor exit node
Delivery
Establish conflux multi-leg circuit with target client
Exploit
Close last linked conflux circuit leg
Execution
Time recovery leg revival to fire post-deallocation
Persist
Trigger use-after-free on conflux object
Impact
Client Tor process crashes

Vulnerability AssessmentAI

Exploitation The attacker must operate a malicious Tor exit node - a significant prerequisite that limits the viable attacker pool to actors with resources and intent to run network infrastructure. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The NVD CVSS 3.1 score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) accurately characterizes the bounded impact: availability-only (client crash), high attack complexity due to required timing alignment and the prerequisite of exit-node control, and no scope change. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An adversary operating a malicious Tor exit node establishes or participates in conflux-enabled multi-leg circuits with a target client, then deliberately closes the last linked conflux leg while engineering a recovery leg to fire shortly after. This triggers the use-after-free on the now-freed conflux object inside the client's Tor process, causing an immediate crash and severing the client's anonymity network connection. …
Remediation Upgrade to Tor 0.4.9.11 or later; this is the vendor-released patch addressing TROVE-2026-026, documented in the official ChangeLog at https://gitlab.torproject.org/tpo/core/tor/-/raw/tor-0.4.9.11/ChangeLog. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

More in Tor

View all
CVE-2017-16541 MEDIUM POC
6.5 Nov 04

Tor Browser before 7.0.9 on macOS and Linux allows remote attackers to bypass the intended anonymity feature and discove

CVE-2021-38385 HIGH POC
7.5 Aug 30

Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-s

CVE-2018-0491 HIGH POC
7.5 Mar 05

A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. Rated high severity (CVSS 7.5), this vulnerability

CVE-2023-23589 MEDIUM POC
6.5 Jan 14

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 th

CVE-2020-8516 MEDIUM POC
5.3 Feb 02

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 att

CVE-2026-77638 HIGH
8.9 Aug 20

Man-in-the-middle impersonation of onion services in Tor before 0.4.9.11 exploits a race condition in rendezvous point c

CVE-2017-8823 HIGH
8.1 Dec 03

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 bef

CVE-2016-1254 HIGH
7.5 Dec 05

Tor before 0.2.8.12 might allow remote attackers to cause a denial of service (client crash) via a crafted hidden servic

CVE-2016-8860 HIGH
7.5 Jan 04

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

CVE-2017-0375 HIGH
7.5 Jun 09

The hidden-service feature in Tor before 0.3.0.8 allows a denial of service (assertion failure and daemon exit) in the r

CVE-2017-0376 HIGH
7.5 Jun 09

The hidden-service feature in Tor before 0.3.0.8 allows a denial of service (assertion failure and daemon exit) in the c

CVE-2017-8821 HIGH
7.5 Dec 03

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 bef

Vendor StatusVendor

SUSE

Severity: Moderate

Share

CVE-2026-77587 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy