cve.bz

CVE-2026-77638 torproject tor: Race Condition

9.0 criticalEPSS 0.3%

Critical (9.0) in torproject tor. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle (impersonate) the onion service that the client was trying to reach.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd 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: total, assessed 2026-08-27. 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-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
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-77638 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77638?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77638?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-77638 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-77638

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-77638](https://cve.bz/cve/badge/CVE-2026-77638.svg)](https://cve.bz/cve/CVE-2026-77638)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
torproject Torfrom 0.3.5.3-alpha before 0.4.9.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12tor0.4.9.11-0+deb12u1DEBIAN-CVE-2026-77638
Debian13tor0.4.9.11-0+deb13u1DEBIAN-CVE-2026-77638
Debian14tor0.4.9.11-1DEBIAN-CVE-2026-77638
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moretorno fix listedUBUNTU-CVE-2026-77638
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.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an untrusted relay functioning as a rendezvous point can subvert cryptographic session binding and fully intercept client communication, although exploitation requires winning a specific timing race. The Tor package is not included with Red Hat Enterprise Linux by default and is only provided through extra community repositories such as EPEL. Systems that do not run Tor or establish circuits to onion services are unaffected by this flaw.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77638.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON