Vulnerability in io.jenkins.plugins:pipeline-groovy-lib (CVE-2026-48921)
Summary
Vulnerability in io.jenkins.plugins:pipeline-groovy-lib (CVE-2026-48921). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 798.v5cc688825312 or later.
Original description
The description as published by the source.
Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries, allowing attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem.
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 vulnerability tracked as CVE-2026-48921 has been found in io.jenkins.plugins:pipeline-groovy-lib.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312 or later.
If unsure, ask your IT team or search "io.jenkins.plugins:pipeline-groovy-lib CVE-2026-48921" on the vendor's site.
CVE-2026-48921 (io.jenkins.plugins:pipeline-groovy-lib) — CWE-59 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 798.v5cc688825312 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in io.jenkins.plugins:pipeline-groovy-lib.
Check the vendor advisory for the affected versions of io.jenkins.plugins:pipeline-groovy-lib.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 798.v5cc688825312.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.jenkins.plugins:pipeline-groovy-lib を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312ステージング環境で 798.v5cc688825312 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch jenkinsci-cert@googlegroups.com
- web github.com