VYPR
Medium severity6.6NVD Advisory· Published May 27, 2026· Updated May 27, 2026

CVE-2026-48918

CVE-2026-48918

Description

Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default, allowing attackers to achieve RCE via crafted referral responses.

Vulnerability

Jenkins Active Directory Plugin versions 2.41 and earlier follows LDAP referrals from the configured Active Directory server by default. A malicious LDAP referral can point to an RMI URL, causing Jenkins to deserialize attacker-controlled data. This affects all installations where the plugin is configured to connect to an Active Directory server. [1]

Exploitation

An attacker who can control the configured Active Directory server (e.g., by compromising it via other means) or who can perform a machine-in-the-middle attack between Jenkins and the LDAP server can send a crafted LDAP referral response. The referral points to an RMI endpoint under the attacker’s control. Jenkins will follow the referral, fetch the serialized object from the RMI server, and attempt to deserialize it. [1]

Impact

Successful exploitation results in remote code execution (RCE) on the Jenkins controller. The attacker gains arbitrary code execution at the privilege level of the Jenkins controller process, which typically has full access to Jenkins configuration, jobs, and secrets. The impact is limited if deserialization gadget chains are not present on the classpath. [1]

Mitigation

Fixed in Active Directory Plugin version 2.41.1, released on 2026-05-27, which no longer follows LDAP referrals by default. Administrators unable to update can start Jenkins with the Java system property -Dhudson.plugins.active_directory.ActiveDirectorySecurityRealm.followReferrals=false to disable referral following as a workaround. [1]

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1