cve.bz

CVE-2026-77642 torproject tor: Out-of-bounds Write

9.3 criticalEPSS 0.4%

Critical (9.3) in torproject tor. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
tor 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. Impact is minor for most Tor roles, but potentially major for directory authorities. This is TROVE-2026-019.

Severity

CVSS 3.1

9.3 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-77642 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77642?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77642?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77642 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-77642

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-77642](https://cve.bz/cve/badge/CVE-2026-77642.svg)](https://cve.bz/cve/CVE-2026-77642)

HTML:

<a href="https://cve.bz/cve/CVE-2026-77642"><img src="https://cve.bz/cve/badge/CVE-2026-77642.svg" alt="CVE-2026-77642"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
torproject Torfrom 0.2.8.2-alpha before 0.4.9.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 14tor0.4.9.9-1DEBIAN-CVE-2026-77642
Debian13tor0.4.9.11-0+deb13u1DEBIAN-CVE-2026-77642
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moretorno fix listedUBUNTU-CVE-2026-77642

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an unauthenticated remote attacker can trigger memory corruption that causes denial of service on systems functioning as directory authorities, potentially disrupting consensus operations. Tor is not included in supported Red Hat Enterprise Linux distributions and is only distributed through community repositories such as EPEL and Fedora. Standard relay and client installations experience minimal exposure, as the heightened operational impact specifically targets directory authorities.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77642.

References

Check your stackJSON