Vulnerability in org.jenkins-ci.plugins:credentials-binding (CVE-2026-48922)
Summary
Vulnerability in org.jenkins-ci.plugins:credentials-binding (CVE-2026-48922). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 725.ve52b or later.
Original description
The description as published by the source.
Jenkins Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, allowing attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem, which can lead to remote code execution if Jenkins is configured to allow a low-privileged user to configure file or zip file credentials used for a job running on the built-in node.
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-48922 has been found in org.jenkins-ci.plugins:credentials-binding.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade org.jenkins-ci.plugins:credentials-binding to 725.ve52b or later.
If unsure, ask your IT team or search "org.jenkins-ci.plugins:credentials-binding CVE-2026-48922" on the vendor's site.
CVE-2026-48922 (org.jenkins-ci.plugins:credentials-binding) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 725.ve52b — 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-20) exists in org.jenkins-ci.plugins:credentials-binding.
Check the vendor advisory for the affected versions of org.jenkins-ci.plugins:credentials-binding.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 725.ve52b.
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・依存マニフェストで org.jenkins-ci.plugins:credentials-binding を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.plugins:credentials-binding to 725.ve52bステージング環境で 725.ve52b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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