Skip to content
Fencer Vulns
medium 5.9

CVE-2026-77587 json

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…

published 2026-08-20 2 mo ago modified 2026-10-18 21 d ago also EUVD-2026-63593

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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.

Patch / fix

  • torproject Tor 0.4.9.11
  • tor Debian 12 0.4.9.11-0+deb12u1
  • tor Debian 13 0.4.9.11-0+deb13u1
  • tor Debian 14 0.4.9.11-1

debian advisories DEBIAN-CVE-2026-77587

  • tor openSUSE Leap 16.0 0.4.9.11-bp160.1.1
  • tor openSUSE Tumbleweed 0.4.9.11-1.1

opensuse advisories openSUSE-SU-2026:21660-1openSUSE-SU-2026:11590-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-77587 updated cvss 5.9

Tor: Tor: Denial of Service via use-after-free vulnerability

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • torproject Tor

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.