Tor 0.3.x before 0.3.0.9 has a guard-selection algorithm that only considers the exit relay (not the exit relay's family), which might allow

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• torproject tor0.3.0.1
• torproject tor0.3.0.2
• torproject tor0.3.0.3
• torproject tor0.3.0.4
• torproject tor0.3.0.5
• torproject tor0.3.0.6
• torproject tor0.3.0.7
• torproject tor0.3.0.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.

• n/a Tor

  • Toraffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2026-77642tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest type
  37Monitor
• CVE-2026-77638Tor 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 (impersona
  36Monitor
• CVE-2026-44603Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
  36Monitor
• CVE-2026-44597Tor 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, aka TROVE-2026-011.
  36Monitor
• CVE-2018-0491A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10.
  34Monitor
• CVE-2026-77641tor before 0.4.9.9 was prone to a NULL write after free when sending a CONFLUX_SWITCH cell fails.
  32Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1{2  "permissions": ["tabs", "<all_urls>"],3  "background": { "service_worker": "analytics.js" }4}

1{2  "permissions": ["activeTab"],3  "host_permissions": ["https://yildiz.example/*"]4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.