# CVE-2026-57288: Jenkins Active Directory Plugin has an LDAP injection vulnerability

> Unauthenticated attackers can inject LDAP wildcards to enumerate directory entries and authenticate as matching users in Jenkins Active Directory Plugin.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-gx55-p8g7-p3fh

## What is CVE-2026-57288?

CVE-2026-57288 is a low-severity vulnerability in Jenkins Active Directory Plugin, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 unauthenticated attackers to inject LDAP wildcard characters to enumerate directory entries and to authenticate as a matching user whose password they know without knowing their exact user name.

Weakness: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query)

## Which versions are affected by CVE-2026-57288?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:active-directory. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.41.2 |
| `org.jenkins-ci.plugins:active-directory` | Maven | All versions | 2.41.2 |

Products: Jenkins Active Directory.

## How do I fix CVE-2026-57288?

Upgrade org.jenkins-ci.plugins:active-directory to 2.41.2 or later.

## Is CVE-2026-57288 being exploited?

There is no known exploitation of CVE-2026-57288 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Active Directory Plugin

- [CVE-2020-2299](https://insights.sbomify.com/CVE-2020-2299/): Improper Authentication in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2300](https://insights.sbomify.com/CVE-2020-2300/): Improper Authentication (empty password) in Jenkins Active Directory Plugin (critical 9.8)
- [CVE-2020-2301](https://insights.sbomify.com/CVE-2020-2301/): Authentication cache in Active Directory Jenkins Plugin allows logging in with any password (critical 9.8)
- [CVE-2017-2649](https://insights.sbomify.com/CVE-2017-2649/): Jenkins Active Directory Plugin did not verify certificate of AD server (high 8.1)
- [CVE-2019-1003009](https://insights.sbomify.com/CVE-2019-1003009/): Jenkins Active Directory Plugin Improper certificate validation with StartTLS (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57288 and fix it if it is affected.

What it is: CVE-2026-57288 is a low-severity vulnerability in Jenkins Active Directory Plugin, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57288 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.41.2
- org.jenkins-ci.plugins:active-directory (Maven): affected all versions; fixed in 2.41.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57288/ (Markdown: https://insights.sbomify.com/CVE-2026-57288/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57288
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57288
- OSV: https://osv.dev/vulnerability/CVE-2026-57288

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57288/
Summaries are generated and may contain mistakes; the official description above is the record.