CVE-2026-77584
highpriority · track · 33EPSS 0.003 · 16 %ileDEUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-2959Tor: Mehrere SchwachstellenDeutsch2026-08-20csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Tor ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, Informationen offenzulegen oder einen Denial-of-Service-Zustand herbeizuführen.
sources
Which sources assert this record, and when.
references (1) nvd
External citations — patches, advisories, analysis.
- https://gitlab.torproject.org/tpo/core/tor/-/raw/tor-0.4.9.10/ChangeLogRelease NotesVendor Advisory
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan