GitHub Advisoryadvisory · Maven
GHSA-wrhr-54p6-q97f Jenkins Active Directory Plugin follows LDAP referrals by default
MEDIUM
Official page ↗
- Aliases
- CVE-2026-48918
- Ecosystem
- Maven
- Packages
- org.jenkins-ci.plugins:active-directory
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-918
- Reviewed
- 2026-07-01
Affected packages
• Maven org.jenkins-ci.plugins:active-directory: < 2.41.1 → fixed in 2.41.1
Description
Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals from the configured Active Directory server by default. These can forward to an RMI URL that causes Jenkins to deserialize attacker-controlled data, resulting in Remote Code Execution (RCE) on the Jenkins controller if deserialization "gadgets" are available on the classpath.
This allows attackers able to control the configured Active Directory server, or able to perform a machine-in-the-middle attack, to execute code on the Jenkins controller.
Active Directory Plugin 2.41.1 no longer follows LDAP referrals by default.
Administrators unable to update to a fixed version can start Jenkins with the Java system property `hudson.plugins.active_directory.referral.ignore` set to `true` to mitigate the vulnerability.
Administrators of Jenkins controllers requiring following LDAP referrals can set the Java system property `hudson.plugins.active_directory.referral.ignore` to `false` to restore the previous behavior.
Related
Alias · CVE (1)
- CVE-2026-48918 Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default. vulnerability
Weakness · CWE (1)
- CWE-918 Server-Side Request Forgery weakness