CVE-2010-1676: Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to

Q: How do I fix CVE-2010-1676?

tor: upgrade to newer than 0.2.1.1.27. Exact commands for each OS are on this page.

Q: Is CVE-2010-1676 being exploited?

CVE-2010-1676 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2010-1676 affect?

CVE-2010-1676 affects tor. Severity is high (CVSS 10.0). Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via unspecified vectors.

Q: How urgent is CVE-2010-1676?

Priority 59/100. Critical severity; EPSS top 5%: very likely to be exploited

This month

HIGH 10.0UPGRADE

CVE-2010-1676 is a high-severity flaw (CVSS 10.0) affecting tor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via unspecified vectors.

Why this priority

Critical severity
EPSS top 5%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score	10.0 (High)
EPSS exploit chance	7.9% (top 5%)
CISA exploited list	No
Weakness	CWE-119
Published	2010-12-22
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: tor

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2010-12-22 01:00 UTCPublished CVE record published
2026-06-16 23:19 UTCUpdated Record last modified

tor tor UPGRADE

Affected: <= 0.2.1.1.27 · 0.0.2 · 0.0.2_pre13 · 0.0.2_pre14 · 0.0.2_pre15 · 0.0.2_pre16 · 0.0.2_pre17 · 0.0.2_pre18

Fixed in: newer than 0.2.1.1.27

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy tor || rpm -q tor || tor --version

2. UPGRADE to newer than 0.2.1.1.27 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade tor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade tor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2010-1676?

tor: upgrade to newer than 0.2.1.1.27. Exact commands for each OS are on this page.

Is CVE-2010-1676 being exploited?

CVE-2010-1676 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2010-1676 affect?

CVE-2010-1676 affects tor. Severity is high (CVSS 10.0). Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via unspecified vectors.

How urgent is CVE-2010-1676?

Priority 59/100. Critical severity; EPSS top 5%: very likely to be exploited

Related CVEs

CVE-2026-44603 LOW 3.7 UPGRADE Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
CVE-2026-44597 LOW 3.7 UPGRADE Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in it
CVE-2026-44600 LOW 3.7 UPGRADE Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka
CVE-2026-44601 LOW 3.7 UPGRADE Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a doub
CVE-2026-44602 LOW 3.7 UPGRADE Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-00

References

← Back to latest CVEs