Vulert records 4 vulnerabilities for gftp in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does gftp have?

4 vulnerabilities are recorded for gftp in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new gftp vulnerabilities disclosed?

0 vulnerabilities were recorded for gftp in the last 12 months, and the oldest entry in this database dates to 02 May 2005. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of gftp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor gftp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the gftp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · Debian · Package report

gftp: vulnerability history, versions and safety

gftp is a package in the Debian ecosystem. Vulert records 4 vulnerabilities for it across 2 affected ranges, from May 2005 to Jul 2007. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

4 vulnerabilities recorded U4

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gftp vulnerabilities

Vulert verdict on gftp i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 25 Jul 2007. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 4 vulnerabilities on record across 2 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

Vulnerabilities on record 4 over 2 years · 0 in the last year i
Latest disclosure 25 Jul 2007 i
Highest CVSS n/a i
With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

Affected range	Vulnerabilities
up to 2.0.18-17 (exclusive)	2
up to 2.0.18-1 (exclusive)	2

02 Disclosure history

How often vulnerabilities are recorded

2005 2
2007 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for gftp

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Multiple off-by-one errors in fsplib.c in fsplib before 0.8	N/A unrated	2.0.18-17	25 Jul 2007
Directory Traversal Vulnerability in gftp: Risk of Arbitrary File Access	N/A unrated	2.0.18-1	02 May 2005
Directory Traversal Vulnerability in gftp: Remote File Access Risk	N/A unrated	2.0.18-1	02 May 2005
Off-by-One Vulnerability in gftp Package Leading to Denial of Service	N/A unrated	2.0.18-17	25 Jul 2007

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315