Cross-Site Request Forgery (CSRF) in io.jenkins.plugins:pipeline-groovy-lib (CVE-2026-57283)
Summary
Vulnerability in io.jenkins.plugins:pipeline-groovy-lib (CVE-2026-57283). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4331.4333 or later.
Original description
The description as published by the source.
Jenkins Pipeline: Groovy Plugin 4331.v9d06ed4658ff and earlier does not restrict the types that can be instantiated through the Pipeline Snippet Generator, instantiating any type with a constructor annotated with @DataBoundConstructor in response to a request.
This allows attackers to have Pipeline: Groovy Plugin instantiate types related to job or system configuration other than Pipeline steps.
Additionally, this HTTP endpoint can be accessed using the GET method and does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. This allows attackers to create a script approval request attributed to another user, impersonating a trusted user when social engineering an administrator into approving a malicious script.
This vulnerability has been reported through the Jenkins Bug Bounty Program sponsored by the European Commission.
Pipeline: Groovy Plugin 4331.4333.v50a_b_076c5199 only instantiates Pipeline steps and metastep delegates through the Snippet Generator, and requires POST requests for the affected HTTP endpoint.
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-57283 has been found in io.jenkins.plugins:pipeline-groovy-lib.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade io.jenkins.plugins:pipeline-groovy-lib to 4331.4333 or later.
If unsure, ask your IT team or search "io.jenkins.plugins:pipeline-groovy-lib CVE-2026-57283" on the vendor's site.
CVE-2026-57283 (io.jenkins.plugins:pipeline-groovy-lib) — CWE-352 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4331.4333 — 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.
CSRF (CWE-352) exists in io.jenkins.plugins:pipeline-groovy-lib.
Check the vendor advisory for the affected versions of io.jenkins.plugins:pipeline-groovy-lib.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 4331.4333.
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 4331.4333ステージング環境で 4331.4333 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web jenkins.io
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com