Incorrect Synchronization Affecting tor package, versions <0.4.9.11-0+deb13u1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-TOR-19166212
  • published22 Aug 2026
  • disclosed20 Aug 2026

Introduced: 20 Aug 2026

NewCVE-2026-77584  (opens in a new tab)
CWE-821  (opens in a new tab)

How to fix?

Upgrade Echo:latest tor to version 0.4.9.11-0+deb13u1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tor package and not the tor package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.