Jenkins Active Directory Plugin has an LDAP injection vulnerability
In Jenkins Active Directory Plugin 2.41.1 and earlier, the Windows native (ADSI) authentication path does not escape the user name before building the LDAP search filter. This allows unauthenticated attackers to inject LDAP wildcard characters into the user name, enabling them to enumerate directory user and group names, and to authenticate as a matching user when they know that user’s password but not their exact user name. Active Directory Plugin 2.41.2 escapes the user name in the Windows native (ADSI) authentication path before building the LDAP search filter.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-57288US | — | — | ||
Jenkins Active Directory Plugin 2.41.1 and earlier does not escape the user name before building the LDAP search filter in the Windows native (ADSI) authentication path, allowing u… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/jenkinsci/active-directory-pluginPACKAGE
- https://github.com/jenkinsci/active-directory-plugin/commit/5028dea8e0acc45ff9d6be302d4e1cbc1f9da464WEB
- https://github.com/jenkinsci/active-directory-plugin/releases/tag/active-directory-2.41.2WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-57288ADVISORY
- https://www.jenkins.io/security/advisory/2026-06-24/#SECURITY-3651WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan