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

CVE-2026-48919

CVE-2026-48919

Description

Jenkins Active Directory Plugin 2.41 and earlier deserializes data from LDAP referrals without validation.

AI Insight

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

Jenkins Active Directory Plugin 2.41 and earlier deserializes attacker-controlled data from LDAP referrals, potentially leading to remote code execution.

Vulnerability

Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals from the configured Active Directory server by default without validating the data received. These referrals can forward to an RMI URL that causes Jenkins to deserialize attacker-controlled data, resulting in a deserialization vulnerability [1]. The affected versions are 2.41 and all earlier releases.

Exploitation

An attacker who can control the configured Active Directory server, or who can perform a machine-in-the-middle attack on the LDAP connection, can craft a malicious LDAP referral that points to an RMI endpoint. When Jenkins follows the referral, it deserializes the attacker-supplied data without validation [1]. No additional authentication or user interaction is required beyond the initial configuration of the Active Directory server.

Impact

Successful exploitation allows an attacker to achieve remote code execution (RCE) on the Jenkins controller if the required deserialization "gadgets" are available on the classpath [1]. The attacker gains full control over the Jenkins controller at the privilege level of the Jenkins process.

Mitigation

Active Directory Plugin version 2.41.1, released on 2026-05-27, no longer follows LDAP referrals by default, mitigating this vulnerability [1]. Administrators unable to update immediately can start Jenkins with the system property -Djenkins.security.FollowLDAPReferrals=false 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