Skip to main content

Tor EUVDEUVD-2026-28238

| CVE-2026-44599 MEDIUM
Incorrect Resource Transfer Between Spheres (CWE-669)
2026-05-07 mitre GHSA-rprm-6mg6-r8fm
5.3
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker positions malicious Tor relay
  2. Delivery
    Target circuit includes attacker relay
  3. Exploit
    Attacker sends BEGIN_DIR cell over conflux leg
  4. Execution
    Tor improperly accepts cell
  5. Persist
    Circuit state corrupted
  6. Impact
    Potential routing integrity violation

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incorrect resource transfer between spheres
Exploitation Conditions

Exploitation requires the target Tor instance to have received or processed a BEGIN_DIR cell over a conflux leg, which occurs only when conflux is enabled (a newer feature not universally deployed). The attacker must either operate a relay that participates in the target's circuit or have network-layer access to intercept and inject Tor protocol cells. Default Tor configurations may not have conflux enabled, further limiting practical exploitation surface. The vulnerability is not remotely triggerable by passive network observation alone; active cell injection is mandatory. Exploitation is restricted to integrity violations within circuit state and does not allow confidentiality breaches (C:N in CVSS) or denial of service (A:N in CVSS).

Impact

The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) indicates network-accessible exploitation with high attack complexity and integrity impact only. The low CVSS score of 3.7 reflects limited practical harm. No EPSS score, KEV listing, or public proof-of-concept code is provided, suggesting this is not actively exploited in the wild. Attack complexity is rated 'High', meaning an attacker must perform non-trivial actions or craft specific conditions to trigger the vulnerability. The integrity impact is isolated (Scope Unchanged) and does not cascade to confidentiality or availability. Risk is further diminished because this attack requires either operating a malicious Tor relay or controlling network conditions to inject crafted BEGIN_DIR cells over conflux legs. For typical Tor users passively consuming circuits, the practical exploitation probability remains low. However, operators running Tor relays or bridges may warrant prompt patching to eliminate the window for directed attacks from relay operators or advanced network adversaries.

Exploit ScenarioDerived

An attacker operating a malicious Tor relay or with network-level packet injection capability sends a crafted BEGIN_DIR cell to a target Tor client or relay over an established conflux leg, triggering improper state handling. Due to the high attack complexity, the attacker must either control a relay in the target's circuit path or achieve sophisticated network positioning (e.g., BGP hijacking, ISP-level MITM) to inject the malicious cell. If successful, the attacker may corrupt the circuit's internal state, potentially allowing subtle integrity violations in routing decisions or onion service operations.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 07, 2026

Tor before version 0.4.9.7 can incorrectly attempt or accept BEGIN_DIR cells over conflux legs, a Tor relay multiplexing feature, enabling potential integrity violations in circuit construction. The vulnerability has a CVSS score of 3.7 (low severity) with impact limited to integrity rather than confidentiality or availability. No public exploit code or active exploitation has been identified at the time of analysis.

RemediationAI

Upgrade Tor to version 0.4.9.7 or later. This is the primary fix provided by the Tor Project and fully resolves the vulnerability by preventing BEGIN_DIR cells from being accepted or processed over conflux legs. No workarounds are available for versions prior to 0.4.9.7. Users unable to upgrade immediately should temporarily disable conflux participation by reviewing relay configuration settings in torrc; however, this may impact performance and routing diversity, so upgrading is strongly preferred. Detailed upgrade instructions and release notes are available at https://forum.torproject.org/c/news/tor-release-announcement/28 and https://www.openwall.com/lists/oss-security/2026/05/06/8.

Affected VersionsENISA

Tor 0 <0.4.9.7

Affected Packages

euvd tor fix: 0.4.9.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability involves Tor's conflux protocol implementation, which allows multiple relay legs to be aggregated into a single circuit for improved routing flexibility and performance. BEGIN_DIR is a Tor cell type used to establish directory connections over existing circuits. The underlying issue (CWE-669: Improper Resource Validation) indicates insufficient validation of which circuit types can legitimately carry BEGIN_DIR cells. Conflux legs are not designed to handle directory protocol streams, and accepting such cells over these specialized legs violates Tor's circuit state machine rules. The vulnerability affects all Tor versions prior to 0.4.9.7, as identified by the CPE string cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:*.

Know when Tor gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

4
Severity Changed
Oct 26, 2026 - 00:23 NVD
LOW MEDIUM
CVSS changed
Oct 26, 2026 - 00:23 NVD
3.7 (LOW) 5.3 (MEDIUM)
Patch available
May 07, 2026 - 06:16 EUVD
CVE Published
May 07, 2026 - 02:11 nvd
LOW 3.7

DescriptionNVD

Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Tor

View all
CVE-2017-16541 MEDIUM POC
6.5 Nov 04

Tor Browser before 7.0.9 on macOS and Linux allows remote attackers to bypass the intended anonymity feature and discove

CVE-2021-38385 HIGH POC
7.5 Aug 30

Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-s

CVE-2018-0491 HIGH POC
7.5 Mar 05

A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. Rated high severity (CVSS 7.5), this vulnerability

CVE-2023-23589 MEDIUM POC
6.5 Jan 14

The SafeSocks option in Tor before 0.4.7.13 has a logic error in which the unsafe SOCKS4 protocol can be used but not th

CVE-2026-77642 CRITICAL
9.3 Aug 20

Out-of-bounds write in The Tor Project's tor daemon (0.2.8.2-alpha through versions before 0.4.9.9) can be triggered whe

CVE-2020-8516 MEDIUM POC
5.3 Feb 02

The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before att

CVE-2026-77638 CRITICAL
9.0 Aug 20

Rendezvous-point impersonation in Tor before 0.4.9.11 lets a malicious relay that a client happens to select as its rend

CVE-2026-77641 HIGH
8.2 Aug 20

Write-after-free in Tor's conflux (traffic-splitting) subsystem allows a remote unauthenticated attacker to crash a Tor

CVE-2026-77584 HIGH
8.2 Aug 20

Use-after-free in Tor's conflux circuit handling allows a malicious Tor client to corrupt relay memory by sending a RELA

CVE-2017-8823 HIGH
8.1 Dec 03

In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and 0.3.1 bef

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy