CVE-2026-109786 In fail2ban 0.10.5 through 1.1.1 before ddd879d, the sshd filter (config/filter.d/sshd.conf) accepts an "on <token>" suffix after the host address. Because OpenSSH logs the offered username verbatim,....
MediumCVSS 5.3
EPSS 0.31%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
- Technology
- UbuntuDebian
Description
In fail2ban 0.10.5 through 1.1.1 before ddd879d, the sshd filter (config/filter.d/sshd.conf) accepts an "on <token>" suffix after the host address. Because OpenSSH logs the offered username verbatim, a remote unauthenticated attacker can use a username such as "x VICTIM-SOURCE-IP-ADDRESS on" to make fail2ban associate failed login attempts with an arbitrary source IP address and ban it (e.g., to block logins from a legitimate user). The default filter mode is affected.
Upgrade path
8 packages: 1 fixed, 7 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| debian/fail2ban(Debian 12) | = 1.0.2-2; = 1.0.2-3; = 1.1.0-1; = 1.1.0-2 +10 more | No fix listed | No fix yet |
| debian/fail2ban(Debian 13) | = 1.1.0-8; = 1.1.0-9; = 1.1.0-10; = 1.1.0-11 +2 more | No fix listed | No fix yet |
| debian/fail2ban(Debian 14) | = 1.1.0-8; = 1.1.0-9; = 1.1.0-10; = 1.1.0-11 +2 more | No fix listed | No fix yet |
| ubuntu/fail2ban(Ubuntu 22.04) | All versions | No fix listed | No fix yet |
| ubuntu/fail2ban(Ubuntu 24.04) | All versions | No fix listed | No fix yet |
| ubuntu/fail2ban(Ubuntu 26.04) | All versions | No fix listed | No fix yet |
| ubuntu/fail2ban(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| fail2ban | >= 0.10.5, <= 1.1.1 | after 1.1.1 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| fail2ban | >= 0.10.5, <= 1.1.1 | No fix listed |
| debian/fail2ban(Debian:12) | All versions | No fix listed |
| debian/fail2ban(Debian:12) | = 1.0.2-2 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.0.2-3 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-1 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-10 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-11 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-2 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-3 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-4 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-6 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-7 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-8 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.0-9 | No fix listed |
| debian/fail2ban(Debian:12) | = 1.1.1-1 | No fix listed |
| debian/fail2ban(Debian:13) | All versions | No fix listed |
| debian/fail2ban(Debian:13) | = 1.1.0-10 | No fix listed |
| debian/fail2ban(Debian:13) | = 1.1.0-11 | No fix listed |
| debian/fail2ban(Debian:13) | = 1.1.0-8 | No fix listed |
| debian/fail2ban(Debian:13) | = 1.1.0-9 | No fix listed |
| debian/fail2ban(Debian:13) | = 1.1.1-1 | No fix listed |
| debian/fail2ban(Debian:14) | All versions | No fix listed |
| debian/fail2ban(Debian:14) | = 1.1.0-10 | No fix listed |
| debian/fail2ban(Debian:14) | = 1.1.0-11 | No fix listed |
| debian/fail2ban(Debian:14) | = 1.1.0-8 | No fix listed |
Show 6 more
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/fail2ban(Debian:14) | = 1.1.0-9 | No fix listed |
| debian/fail2ban(Debian:14) | = 1.1.1-1 | No fix listed |
| ubuntu/fail2ban(Ubuntu:22.04) | All versions | No fix listed |
| ubuntu/fail2ban(Ubuntu:24.04) | All versions | No fix listed |
| ubuntu/fail2ban(Ubuntu:26.04) | All versions | No fix listed |
| ubuntu/fail2ban(Ubuntu:26.10) | All versions | No fix listed |
References
- github.com patch
- coredump.ws related
- Debian Security Tracker CVE-2026-109786 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- www.cve.org
- bugs.debian.org issue-tracking
- ENISA EUVD EUVD-2026-98268 third-party-advisory