dbcve.org
Active DirectoryApplication · Jenkins

CVE-2026-48918

MEDIUM · 6.6 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 2.41 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Jenkins Active Directory Plugin versions 2.41 and earlier follows LDAP referrals by default during authentication. This means when an LDAP server returns a referral to another LDAP server, the plugin automatically follows that referral and attempts authentication against the referred server, potentially allowing authentication against untrusted or malicious LDAP servers.

MitigationUpdate the Jenkins Active Directory Plugin to a version newer than 2.41 and configure the plugin to disable automatic LDAP referral following to prevent authentication against untrusted servers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Active DirectoryApplication
Affected:<= 2.41

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Jenkins Active Directory plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or inspect $JENKINS_HOME/plugins/ for ad-auth-plugin or active-directory directory
    Affected if Plugin is present in the Jenkins instance
  2. Check the Active Directory plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the Active Directory plugin version; or read the manifest file in $JENKINS_HOME/plugins/active-directory/META-INF/MANIFEST.MF
    Affected if Installed version is 2.41 or lower
  3. Confirm LDAP/Active Directory authentication is enabled
    Navigate to Manage Jenkins > Configure Global Security > Security Realm and verify 'Active Directory' or 'LDAP' is selected as the Security Realm
    Affected if LDAP or Active Directory authentication is configured as the security realm
  4. Check LDAP referral following configuration
    In Manage Jenkins > Configure Global Security > Active Directory domain configuration, inspect whether 'Follow LDAP referrals' or similar option is enabled (default behavior is to follow)
    Affected if Referral following is not explicitly disabled, or the setting is not visible (default is to follow)

If the Active Directory plugin version is 2.41 or lower and LDAP/AD authentication is configured, the environment is affected because the plugin follows LDAP referrals by default.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.41
Interim mitigation

Update the Jenkins Active Directory Plugin to a version newer than 2.41 and configure the plugin to disable automatic LDAP referral following to prevent authentication against untrusted servers.

Recommended fix Moderate confidence

Active Directory plugin version 2.42 or later (verify exact version from Jenkins security advisory)

  1. Check the Jenkins security advisory on www.jenkins.io for the specific fix version for this CVE
  2. Navigate to Manage Jenkins > Manage Plugins > Installed
  3. Locate the 'Active Directory' plugin in the list
  4. If an update is available, review the changelog for version 2.42 or later
  5. Apply the plugin update
  6. Restart Jenkins if required by the update
  7. Alternatively, if no update is available, navigate to the Active Directory plugin configuration and disable 'Follow LDAP referrals' if that option is exposed in your version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Active Directory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48918 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data