Bug 2543863 (CVE-2026-94053)

Summary:	CVE-2026-94053 org.apache.sshd/sshd-ldap: Apache MINA SSHD: LDAP injection in sshd-ldap
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	unspecified	Keywords:	Security
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the sshd-ldap component of Apache MINA SSHD. This vulnerability allows an unauthenticated remote attacker to bypass authentication due to improper escaping of LDAP (Lightweight Directory Access Protocol) filter metacharacters during credential verification. By supplying specially crafted inputs such as wildcard characters, an attacker can authenticate successfully without valid credentials and gain unauthorized access to the SSH server.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2543932
Bug Blocks:

Description OSIDB Bzimport 2026-09-30 10:13:42 UTC

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.