CVE-2026-94053: Apache MINA SSHD: LDAP injection in sshd-ldap
Authentication bypass via LDAP injection in component sshd-ldap in Apache MINA SSHD versions 1.2.0 to 2.19.0 and 3.0.0-M1 to 3.0.0-M5.
Apache MINA SSHD is a Java library for client-side and server-side SSH. The optional sshd-ldap component provides support for integrating password and publickey authentication on the server side with an LDAP server.
sshd-ldap is an optional component. SSH servers implemented with Apache MINA SSHD are affected only if they use sshd-ldap and do configure it to be used for password of public key authentication.
Other Apache MINA SSHD servers are not affected.
Lack of escaping LDAP filter metacharacters enabled successful authentication with username "" and password "".
Users are recommended to upgrade affected applications to version 2.20.0 or 3.0.0-M6, which fix this issue by properly escaping filter parameters according to RFC 4515.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache MINA SSHDto a version that resolves this vulnerability.Fixed in 2.20.0 - Upgrade
Upgrade
Apache MINA SSHDto a version that resolves this vulnerability.Fixed in 3.0.0-M6
Event History
Frequently Asked Questions
Which deployments are affected?
Only SSH servers built with Apache MINA SSHD that include the optional sshd-ldap component and configure it for password or public-key authentication against LDAP are affected. MINA SSHD servers that do not use sshd-ldap are not affected.
What does an attacker need to exploit this issue?
The issue can be exploited remotely without prior privileges or user interaction when the affected LDAP authentication configuration is exposed through the SSH server. Successful authentication was possible using the username "*" and password "*".
How can I remediate the vulnerability?
Upgrade affected applications to Apache MINA SSHD version 2.20.0 or 3.0.0-M6. These versions escape LDAP filter parameters according to RFC 4515.
What can be done if an upgrade cannot be applied immediately?
Disable use of sshd-ldap for password and public-key authentication, or remove the sshd-ldap component from the affected SSH server configuration. Servers not using this optional LDAP authentication component are not affected.