Jenkins Pipeline: Groovy Plugin vulnerable to unrestricted instantiation of types
CVE-2026-57284GHSA-2w2h-gwwj-fh3q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.jenkins.plugins:pipeline-groovy-lib 4331.4333), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven io.jenkins.plugins:pipeline-groovy-lib
- Affected
- < 4331.4333
- Fixed in
- 4331.4333
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2w2h-gwwj-fh3q lists affected ranges: Maven io.jenkins.plugins:pipeline-groovy-lib >=0 <4331.4333
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- EPSS
- CVE-2026-57284: 0.34% estimated exploitation activity in the next 30 days; percentile 27.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.v50ab076c5199 only instantiates Pipeline steps and metastep delegates through the Snippet…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-2w2h-gwwj-fh3q
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-57284 Advisory: Jenkins Pipeline: Groovy Plugin vulnerable to unrestricted instantiation of types IDs: CVE-2026-57284, GHSA-2w2h-gwwj-fh3q Record: https://patchnext.com/advisories/cve-2026-57284 (revision 1, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: io.jenkins.plugins:pipeline-groovy-lib 4331.4333. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven io.jenkins.plugins:pipeline-groovy-lib: affected < 4331.4333; fixed in 4331.4333 ## Suggested inspection (read-only) - Maven io.jenkins.plugins:pipeline-groovy-lib: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on io.jenkins.plugins:pipeline-groovy-lib. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-2w2h-gwwj-fh3q (GitHub-reviewed advisory GHSA-2w2h-gwwj-fh3q lists affected ranges: Maven io.jenkins.plugins:pipeline-groovy-lib >=0 <4331.4333) Commands are suggestions: review each one before running it.
Loading voting…