Description
Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAY_COMMAND_BEGIN before the CONFLUX_LINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit back-pointer and a use-after-free (UAF) when the circuit is freed. This is TROVE-2026-025.
Published: 2026-08-20
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Tor processes a CONFLUX_LINK cell that appears on an existing circuit with attached streams, which normally should be rejected. A malicious client can first issue a RELAY_COMMAND_BEGIN to attach a stream and then send the offending CONFLUX_LINK. The circuit later frees a back‑pointer that is still referenced by the orphaned stream, triggering a use‑after‑free. This memory corruption can lead to a denial of service or arbitrary code execution, a classic CWE‑821 flaw.

Affected Systems

Tor by the Tor Project, versions earlier than 0.4.9.10. Any Tor relay or client running 0.4.9.9 or older is susceptible; upgrades to 0.4.9.10 or newer eliminate the bug.

Risk and Exploitability

The CVSS score of 7 indicates high severity, but the EPSS score is not available and the flaw is not in the CISA KEV catalog. The likely attack vector is a remote client that can control the circuit; successful exploitation requires the attacker to send a RELAY_COMMAND_BEGIN followed by a CONFLUX_LINK, which is feasible over the normal Tor protocol. Given the lack of a public exploit, the immediate danger is moderate, but the potential impact is significant should an attacker trigger the UAF.

Generated by OpenCVE AI on August 21, 2026 at 01:18 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Tor to 0.4.9.10 or later.
  • If immediate upgrade is impossible, configure the node to reject CONFLUX_LINK cells on active circuits, or disable the CONFLUX functionality via configuration options if available.
  • Implement firewall or rate‑limiting rules to restrict anomalous RELAY_COMMAND_BEGIN sequences and monitor logs for orphaned stream or circuit errors.

Generated by OpenCVE AI on August 21, 2026 at 01:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 21 Aug 2026 01:45:00 +0000

Type Values Removed Values Added
Title Use‑After‑Free via CONFLUX_LINK Handling

Thu, 20 Aug 2026 21:00:00 +0000

Type Values Removed Values Added
Description Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a RELAY_COMMAND_BEGIN before the CONFLUX_LINK on the same circuit, attaching an exit stream that would later end up orphan leaving a dangling circuit back-pointer and a use-after-free (UAF) when the circuit is freed. This is TROVE-2026-025.
First Time appeared Torproject
Torproject tor
Weaknesses CWE-821
CPEs cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*
Vendors & Products Torproject
Torproject tor
References
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2026-08-25T19:09:53.308Z

Reserved: 2026-08-20T20:38:41.768Z

Link: CVE-2026-77584

cve-icon Vulnrichment

Updated: 2026-08-25T19:09:44.973Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-20T21:17:10.810

Modified: 2026-09-03T17:37:43.450

Link: CVE-2026-77584

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T02:00:04Z

Weaknesses
  • CWE-821

    Incorrect Synchronization