Use‑After‑Free via CONFLUX_LINK Handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| torproject | Tor | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Torproject | Tor |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.250% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Use‑After‑Free via CONFLUX_LINK Handling |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| First Time appeared |
Torproject
Torproject tor |
|
| Weaknesses | CWE-821 | |
| CPEs | cpe:2.3:a:torproject:tor:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Torproject
Torproject tor |
|
| References |
| |
| Metrics |
cvssV3_1
|