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
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 0.4.9.7 when convenient.
Data as of 27 Oct 2026, 02:41 UTC
- 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:LExploitation evidence
Disclosed: evidence found.
CVE published 7 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| torprojectTor | Affected
| Fixed in
|
AI-suggested
A fixed version 0.4.9.7 or later should be applied once available. Until then, cautious handling of untrusted input and network traffic is advised.
Description
Tor versions prior to 0.4.9.7 contain an out-of-bounds read vulnerability caused by processing a malformed BEGIN cell. This flaw allows reading one byte beyond the intended buffer boundary, potentially leading to application instability or denial of service.
References
- nvd.nist.gov/vuln/detail/CVE-2026-44603 (opens in a new tab)
- forum.torproject.org/c/news/tor-release-announcement/28 (opens in a new tab)
- gitlab.torproject.org/tpo/core/tor/-/commit/1703df3d439c83c2184e259fad1cfa19240f9c89 (opens in a new tab)
- gitlab.torproject.org/tpo/core/tor/-/work_items/41245 (opens in a new tab)
- openwall.com/lists/oss-security/2026/05/06/8 (opens in a new tab)