| CVE-2026-77642 |
tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected…
|
7.5
High
|
Aug 20, 2026 |
| CVE-2026-77641 |
tor before 0.4.9.9 was prone to a NULL write after free when sending a CONFLUX_SWITCH cell fails
|
6.5
Medium
|
Aug 20, 2026 |
| CVE-2026-77640 |
tor before 0.4.9.9 was prone to an infinite loop when decompressing a truncated zlib/gzip stream with done=1
|
3.7
Low
|
Aug 20, 2026 |
| CVE-2026-77639 |
Tor before 0.4.9.9 was prone to a compression bomb bypass where an attacker could concatenate many gzip or zlib…
|
5.3
Medium
|
Aug 20, 2026 |
| CVE-2026-77638 |
Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could…
|
8.9
High
|
Aug 20, 2026 |
| CVE-2026-77587 |
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…
|
5.9
Medium
|
Aug 20, 2026 |
| CVE-2026-77584 |
Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams
|
7.0
High
|
Aug 20, 2026 |
| CVE-2026-44603 |
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007
|
3.7
Low
|
May 7, 2026 |
| CVE-2026-44602 |
Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006
|
3.7
Low
|
May 7, 2026 |
| CVE-2026-44601 |
Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a double close…
|
3.7
Low
|
May 7, 2026 |
| CVE-2026-44600 |
Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka…
|
3.7
Low
|
May 7, 2026 |
| CVE-2026-44599 |
Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008
|
3.7
Low
|
May 7, 2026 |
| CVE-2026-44597 |
Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in its payload,…
|
3.7
Low
|
May 7, 2026 |