Cyber Resilience

CVE-2026-57288

Jenkins Active Directory ≤ 2.41.2

Published
24 June 2026
Modified
26 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0022 13th percentile
Risk Priority 31 floored blend · peak EPSS

Summary

CVE-2026-57288 is a low-severity LDAP Injection (CWE-90) vulnerability in Jenkins Active Directory. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

authenticate as a matching user whose password they know without knowing their exact user name.

CWE(s)
CWE-90

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-48918Same product: Jenkins Active Directory
CVE-2026-48919Same product: Jenkins Active Directory
CVE-2023-37943Same product: Jenkins Active Directory
CVE-2026-48916Same product class: directory / identity
CVE-2023-3447Same product class: directory / identity
CVE-2026-48917Same product class: directory / identity
CVE-2016-9299Same vendor: Jenkins
CVE-2023-50766Same vendor: Jenkins
CVE-2024-23902Same vendor: Jenkins
CVE-2025-64141Same vendor: Jenkins

Affected Assets

jenkins
active directory
≤ 2.41.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

A.8.27 Secure system architecture and engineering principles none match
mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

A.8.3 Information access restriction none match
none

Information access restriction limits who can query LDAP but does not address how queries are built.

References