cve.bz

CVE-2026-77584 torproject tor: Incorrect Synchronization

8.2 highEPSS 0.2%

High (8.2) in torproject tor. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-821 Incorrect Synchronization
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-77584 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77584?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77584?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77584 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-77584

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-77584](https://cve.bz/cve/badge/CVE-2026-77584.svg)](https://cve.bz/cve/CVE-2026-77584)

HTML:

<a href="https://cve.bz/cve/CVE-2026-77584"><img src="https://cve.bz/cve/badge/CVE-2026-77584.svg" alt="CVE-2026-77584"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
torproject Torfrom 0.4.8.1-alpha before 0.4.9.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12tor0.4.9.11-0+deb12u1DEBIAN-CVE-2026-77584
Debian13tor0.4.9.11-0+deb13u1DEBIAN-CVE-2026-77584
Debian14tor0.4.9.11-1DEBIAN-CVE-2026-77584
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moretorno fix listedUBUNTU-CVE-2026-77584
openSUSELeap 16.0tor0.4.9.11-bp160.1.1openSUSE-SU-2026:21660-1
openSUSETumbleweedtor0.4.9.11-1.1openSUSE-SU-2026:11590-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

References

Check your stackJSON