VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

fail2ban: vulnerability history, versions and safety

fail2ban is a package in the Debian ecosystem. Vulert records 16 vulnerabilities for it across 16 releases, from Aug 2007 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded U16
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 26 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fail2ban vulnerabilities

Vulert verdict on fail2ban i

Updated on 23 Oct 2026

Careful: one of the 16 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 18 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 18 years · 1 in the last year i
  • Latest disclosure 26 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 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.

01 Versions

Which versions are affected

Every version Vulert holds for fail2ban, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 16 of 16 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 2
  • 2009 2
  • 2012 2
  • 2013 2
  • 2014 6
  • 2021 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for fail2ban

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Host Addition in fail2ban N/A unrated 0.8.0-4 14 Aug 2007
Critical Vulnerability in fail2ban: Improper SSHD Log File Parsing N/A unrated 0.8.0-4 14 Aug 2007
Remote Code Execution Vulnerability in fail2ban Package N/A unrated 0.11.2-2 16 Jul 2021
Denial of Service Vulnerability in Fail2ban due to Incorrect Regular Expression N/A unrated 0.8.3-2sid1 13 Feb 2009
Remote IP Blocking Vulnerability in Fail2ban: CVE-2013-2178 N/A unrated 0.8.10-1 28 Aug 2013

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About fail2ban

Is fail2ban safe to use?

Vulert records 16 vulnerabilities for fail2ban in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 16 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does fail2ban have?

16 vulnerabilities are recorded for fail2ban in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 16 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 fail2ban vulnerabilities disclosed?

1 vulnerability was recorded for fail2ban in the last 12 months, and the oldest entry in this database dates to 14 Aug 2007. 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 fail2ban 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 fail2ban for upcoming vulnerabilities?

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