cve.bz

CVE-2026-77640 torproject tor

5.3 mediumEPSS 0.4%

Medium (5.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 infinite loop when decompressing a truncated zlib/gzip stream with done=1. A truncated stream never reaches Z_STREAM_END, causing zlib to return Z_BUF_ERROR with no input remaining, which buf_add_compress() mistook for a full output buffer and retried forever. Fixed by returning TOR_COMPRESS_ERROR in that case so the caller can abort cleanly. This is TROVE-2026-021.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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; 32nd 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-21. 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-1284 Improper Validation of Specified Quantity in Input
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-77640 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77640?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77640?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-77640 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-77640

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-77640](https://cve.bz/cve/badge/CVE-2026-77640.svg)](https://cve.bz/cve/CVE-2026-77640)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
torproject Torfrom 0.2.6.1-alpha before 0.4.9.9

Linux distributions

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

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.

References

Check your stackJSON