CVE-2009-1759: Stack-based buffer overflow in the btFiles::BuildFromMI function (trunk/btfiles.cpp) in Enhanced CTorrent (aka

This week

HIGH 9.3DOWNGRADEDOWNGRADE

CVE-2009-1759 is a high-severity flaw (CVSS 9.3) affecting dtorrent, ctorrent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Stack-based buffer overflow in the btFiles::BuildFromMI function (trunk/btfiles.cpp) in Enhanced CTorrent (aka dTorrent) 3.3.2 and probably earlier, and CTorrent 1.3.4, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Torrent file containing a long path.

Why this priority

Critical severity
EPSS top 4%: very likely to be exploited
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.3 (High)
EPSS exploit chance	13.7% (top 4%)
CISA exploited list	No
Weakness	CWE-119
Published	2009-05-22
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: rahul

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

Am I affected?

Timeline

2009-05-22 11:52 UTCPublished CVE record published
2026-06-16 23:07 UTCUpdated Record last modified

rahul dtorrent DOWNGRADE

Affected: 3.2.0 · 3.3.0 · 3.3.1 · 3.3.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 3.2.0 (Debian / Ubuntu)

apt-cache madison dtorrent sudo apt install dtorrent=<VERSION_BEFORE_3.2.0> sudo apt-mark hold dtorrent

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list dtorrent sudo dnf downgrade dtorrent-<VERSION_BEFORE_3.2.0> sudo dnf versionlock add dtorrent

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

rahul ctorrent DOWNGRADE

Affected: 1.3.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.3.4

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 1.3.4 (Debian / Ubuntu)

apt-cache madison ctorrent sudo apt install ctorrent=<VERSION_BEFORE_1.3.4> sudo apt-mark hold ctorrent

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ctorrent sudo dnf downgrade ctorrent-<VERSION_BEFORE_1.3.4> sudo dnf versionlock add ctorrent

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: cTorrent/DTorrent - '.torrent' Local Buffer Overflow

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-2009-1759?

dtorrent: downgrade or apply the listed mitigation; ctorrent: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-1759 being exploited?

CVE-2009-1759 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-2009-1759 affect?

CVE-2009-1759 affects dtorrent, ctorrent. Severity is high (CVSS 9.3). Stack-based buffer overflow in the btFiles::BuildFromMI function (trunk/btfiles.cpp) in Enhanced CTorrent (aka dTorrent) 3.3.2 and probably earlier, and CTorrent 1.3.4, allows remote attackers to cause a denial of service (crash) and possib

How urgent is CVE-2009-1759?

Priority 62/100. Critical severity; EPSS top 4%: very likely to be exploited; Public exploit reference

References

← Back to latest CVEs