Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessEstablish TLS connection to Tor relay
-
DeliveryComplete Tor handshake protocol
-
ExploitCreate valid circuit
-
ExecutionSend malformed BEGIN cell
-
PersistTrigger out-of-bounds read
-
ImpactLeak memory or cause denial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Off-by-one prevention
|
| Exploitation Conditions | The target must be running Tor version 0.4.9.6 or earlier and must have the relay or exit port open to network connections (not running as a client-only instance, though clients also process incoming cells). The attacker must send the malformed BEGIN cell as part of an established Tor circuit; raw or unauthenticated cell transmission will not trigger the vulnerability because Tor requires a valid handshake and TLS layer before processing BEGIN cells. No special Tor configuration is required - default relay configurations are vulnerable. The attack is fundamentally limited by the requirement to establish a valid TLS connection and circuit prior to sending the malicious cell, which explains the high attack complexity rating in CVSS. |
| Impact | The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L) indicates network-accessible remote code, but with high attack complexity, making practical exploitation difficult. The availability impact is limited (A:L), and no confidentiality or integrity impact is rated, contradicting the description's mention of 'information disclosure' - this discrepancy suggests either the CVSS underestimates the C impact or the description overstates it. No KEV status, EPSS score, or POC availability data is provided. The attack requires crafting a malformed BEGIN cell and sending it to a Tor relay, which requires network access to a relay and understanding of Tor's cell format. The high attack complexity combined with limited impact and lack of public exploitation evidence suggests this is a lower-priority issue than the CVSS number alone would indicate, but its network accessibility and lack of authentication requirements mean it is not trivial to ignore in production Tor deployments. |
| Exploit ScenarioDerived | An attacker with network access to a Tor relay crafts a malformed BEGIN cell with an incorrect length field or structure. When the relay processes this cell during circuit handling, the parser reads one byte past the allocated buffer boundary. Depending on the memory layout at that time, this could leak a byte of memory containing sensitive data such as circuit keys or cause the relay process to crash, disrupting service. An attacker would need to know the target is running a vulnerable Tor version and establish a connection to its relay port (typically 6667 or custom), then send the malformed cell within a valid Tor handshake and circuit setup sequence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 07, 2026
Out-of-bounds read by one byte in Tor before version 0.4.9.7 when processing malformed BEGIN cells allows remote unauthenticated attackers to cause a denial of service through information disclosure. The vulnerability has a low CVSS impact score (3.7) due to high attack complexity and limited availability impact, though the exact exploitation mechanics require Tor relay configuration and a specially crafted cell.
RemediationAI
Upgrade Tor to version 0.4.9.7 or later immediately. This fix is available via the official Tor Project release channels at https://forum.torproject.org/c/news/tor-release-announcement/28. Users should run 'tor --version' to check their current version and update through their operating system package manager (apt, yum, brew, etc.) or by downloading the latest stable release from torproject.org. For users unable to patch immediately, restrict inbound connections to Tor relays to trusted sources if operating a relay; however, this is not a true workaround since Tor's design requires accepting connections from unknown peers. The recommended approach is prompt patching, as the fix has been available upstream and integrated into the stable release cycle.
Affected VersionsENISA
Affected Packages
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
Tor is an anonymization network that routes traffic through multiple relays using a cell-based protocol. The vulnerability exists in the BEGIN cell handler, which is part of Tor's circuit building protocol. A BEGIN cell initiates a new stream over an existing circuit. The out-of-bounds read (CWE-193: Off-by-one error) occurs when parsing a malformed BEGIN cell, allowing an attacker to read one byte of memory beyond the intended buffer boundary. This memory access violation could leak sensitive information from the Tor process memory or trigger an availability disruption depending on the memory region accessed.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Related Vulnerabilities in Tor Protocol Implementation Flaws
View all 6Tor Browser before 7.0.9 on macOS and Linux allows remote attackers to bypass the intended anonymity feature and discove
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
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
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
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
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
Rendezvous-point impersonation in Tor before 0.4.9.11 lets a malicious relay that a client happens to select as its rend
Write-after-free in Tor's conflux (traffic-splitting) subsystem allows a remote unauthenticated attacker to crash a Tor
Use-after-free in Tor's conflux circuit handling allows a malicious Tor client to corrupt relay memory by sending a RELA
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
Tor before 0.2.8.12 might allow remote attackers to cause a denial of service (client crash) via a crafted hidden servic
EUVD-2026-28306
GHSA-m47q-4224-6rvc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB