Quick answers
- Is CVE-2026-57288 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57288 being exploited in the wild.
- How severe is CVE-2026-57288?
- Low severity, with a CVSS score of 3.7, published 24 June 2026.
- Which products and versions are affected?
- org.jenkins-ci.plugins:active-directory (Maven) < 2.41.2, ECOSYSTEM:introduced=0,fixed=2.41.2.
- Is there a fix for CVE-2026-57288?
- Yes. org.jenkins-ci.plugins:active-directory (Maven): upgrade to 2.41.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57288 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57288?
- Check whether you run org.jenkins-ci.plugins:active-directory (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.jenkins-ci.plugins:active-directory (Maven): upgrade to 2.41.2 or later
# set org.jenkins-ci.plugins:active-directory to 2.41.2 in your pom.xml or build.gradle
Technical details
The vulnerability exists in the Windows native (ADSI) authentication path of the Jenkins Active Directory Plugin. Due to a failure to sanitize or escape the username field before it is incorporated into an LDAP search filter, the component is susceptible to LDAP injection. An unauthenticated attacker can use LDAP wildcard characters (e.g., '*') to enumerate directory entries. Furthermore, an attacker who possesses a valid password for a user account can successfully authenticate without knowing the exact username by using wildcards to match the target entry. This issue affects versions 2.41.1 and earlier.
Affected products
- Jenkins Project Active Directory Plugin 2.41.1 and earlier
Identifiers
- CVE-2026-57288
- GHSA-gx55-p8g7-p3fh
Timeline
- 2026-06-24: disclosed
- 2026-06-24: advisory