CVE-2026-48918
Analyzed Analyzed - Analysis Complete
LDAP Referral Following in Jenkins Active Directory Plugin

Publication date: 2026-05-27

Last updated on: 2026-05-28

Assigner: Jenkins Project

Description
Jenkins Active Directory Plugin 2.41 and earlier follows LDAP referrals by default.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-05-28
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
jenkins active_directory to 2.41 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The vulnerability in Jenkins Active Directory Plugin version 2.41 and earlier is that it follows LDAP referrals by default.

Impact Analysis

This vulnerability in Jenkins Active Directory Plugin 2.41 and earlier allows the plugin to follow LDAP referrals by default. This behavior can lead to unauthorized access or exposure of sensitive information within the LDAP directory, potentially resulting in confidentiality, integrity, and availability impacts.

Detection Guidance

This vulnerability involves the Jenkins Active Directory Plugin following LDAP referrals by default, which can be exploited if an attacker controls the LDAP server or performs a man-in-the-middle attack.

To detect if your system is vulnerable, you should check the version of the Jenkins Active Directory Plugin installed and verify if it is version 2.41 or earlier.

Additionally, monitoring LDAP traffic for unexpected referrals or unusual LDAP server responses could help identify exploitation attempts.

Suggested commands to check the plugin version on the Jenkins server include:

  • Using Jenkins CLI or UI to list installed plugins and their versions.
  • On the Jenkins server, you can check the plugin directory, for example: `ls $JENKINS_HOME/plugins/active-directory/` and inspect the plugin manifest or version files.

For network detection, you can use tools like tcpdump or Wireshark to capture LDAP traffic and filter for referral messages (LDAP referral responses typically have specific LDAP result codes). Example tcpdump command:

  • tcpdump -i <interface> -s 0 -w ldap_traffic.pcap port 389 or port 636
  • Then analyze ldap_traffic.pcap in Wireshark for LDAP referral responses.
Mitigation Strategies

The primary mitigation is to upgrade the Jenkins Active Directory Plugin to a version later than 2.41 that disables automatic following of LDAP referrals by default.

If upgrading immediately is not possible, consider configuring the plugin or Jenkins to disable following LDAP referrals manually, if such configuration options exist.

Additionally, ensure that your LDAP servers are trusted and protected against man-in-the-middle attacks to reduce the risk of exploitation.

Monitoring and restricting network access to the LDAP service and Jenkins controller can also help mitigate potential attacks.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48918. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart