Improper Output Neutralization for Logs Affecting fail2ban package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.31% (23rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-FAIL2BAN-20877240
  • published13 Oct 2026
  • disclosed13 Oct 2026

Introduced: 13 Oct 2026

NewCVE-2026-109786  (opens in a new tab)
CWE-117  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest fail2ban.

NVD Description

Note: Versions mentioned in the description apply only to the upstream fail2ban package and not the fail2ban package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.