CVE-2026-48917
Description
Jenkins LDAP Plugin 807.v7d7de30930cf and earlier deserializes data from LDAP referrals without validation.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Jenkins LDAP Plugin 807.v7d7de30930cf and earlier deserializes attacker-controlled data from LDAP referrals, enabling RCE if deserialization gadgets are present.
Vulnerability
Jenkins LDAP Plugin versions 807.v7d7de30930cf and earlier follow LDAP referrals from the configured LDAP server. These referrals can forward to an RMI URL, causing Jenkins to deserialize attacker-controlled data without any validation [1]. This deserialization can lead to remote code execution if deserialization gadgets are available on the classpath [1].
Exploitation
An attacker must either control the configured LDAP server or be able to perform a machine-in-the-middle attack to inject a malicious referral. The referral points to an RMI URL containing attacker-controlled serialized data. When Jenkins processes the referral, it deserializes the data, potentially triggering arbitrary code execution [1].
Impact
Successful exploitation allows an attacker to execute arbitrary code on the Jenkins controller with the privileges of the Jenkins process. This results in full compromise of the Jenkins instance, including access to secrets, builds, and configurations [1].
Mitigation
The vulnerability is fixed in LDAP Plugin version 807.809.vd3a_4e5e4ec98, which no longer follows LDAP referrals. Users should update to this version or later. If unable to update, administrators can disable referral following using a Java system property as a workaround (see advisory [1] for details).
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<=807.v7d7de30930cf+ 1 more
- (no CPE)range: <=807.v7d7de30930cf
- (no CPE)range: <=807.v7d7de30930cf
Patches
0No 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
1News mentions
1- Jenkins Security Advisory 2026-05-27Jenkins Security Advisories · May 27, 2026