Skip to content

Jenkins Active Directory Plugin deserializes data from LDAP referrals without validation

Moderate severity GitHub Reviewed Published May 27, 2026 to the GitHub Advisory Database • Updated Jul 1, 2026

Package

maven org.jenkins-ci.plugins:active-directory (Maven)

Affected versions

< 2.41.1

Patched versions

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.

References

Published by the National Vulnerability Database May 27, 2026
Published to the GitHub Advisory Database May 27, 2026
Reviewed Jul 1, 2026
Last updated Jul 1, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(19th percentile)

Weaknesses

Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. Learn more on MITRE.

CVE ID

CVE-2026-48919

GHSA ID

GHSA-p2gw-f3rv-82mw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.