Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48918 medium CVSS 6.6

SSRF (Server-Side Request Forgery) in org.jenkins-ci.plugins:active-directory (CVE-2026-48918)

Summary

SSRF in org.jenkins-ci.plugins:active-directory (CVE-2026-48918). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.41.1 or later.

Original description

The description as published by the source.

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

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2026-48918 was discovered in org.jenkins-ci.plugins:active-directory.
In plain terms, it is an SSRF flaw that lets attackers probe internal networks.
Severity is Medium (CVSS 6.6/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "org.jenkins-ci.plugins:active-directory CVE-2026-48918".

CVE-2026-48918 (org.jenkins-ci.plugins:active-directory). Severity: Medium / CVSSv3 6.6. Category: CWE-918.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-48918) in org.jenkins-ci.plugins:active-directory. In plain words, it is an SSRF flaw that lets attackers probe internal networks.

📍 Affected scope

Target versions of org.jenkins-ci.plugins:active-directory (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Medium (CVSS 6.6/10). Exploitation requires specific conditions but can cause real harm if successful.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-918)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.jenkins-ci.plugins:active-directory を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.jenkins-ci.plugins:active-directory to 2.41.1

    ステージング環境で 2.41.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.jenkins-ci.plugins:active-directory
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.41.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details