Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Authoritative record:CVE-2026-44597· Low 3.7

Not known to be exploited · CVSS 3.7 Low : upgrade to 0.4.9.7 when convenient.

Data as of 27 Oct 2026, 02:39 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.4.9.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Tor to 0.4.9.7.

Affected software

ProductAffectedFixed in
torprojectTorAffected
  • <0.4.9.7
Fixed in
  • 0.4.9.7

AI-suggested

A fix is available in Tor version 0.4.9.7. Users should upgrade to version 0.4.9.7 or later to remediate this vulnerability. No additional mitigation steps are indicated.

Description

Tor versions before 0.4.9.7 contain an out-of-bounds read vulnerability triggered when an END, TRUNCATE, or TRUNCATED cell lacks a reason in its payload. This flaw is identified as CVE-2026-44597 and is also known as TROVE-2026-011. The vulnerability has a low severity rating and does not impact confidentiality or integrity but may cause a denial of service due to application instability.

References

Community reviews

Loading reviews…