Skip to content

← Actionable
High, CVSS 7.5

Sandbox bypass vulnerability through implicitly allowlisted platform Groovy files in Jenkins Pipeline: Groovy Plugin

CVE-2022-30945GHSA-2xvx-rw9p-xgfc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.jenkins-ci.plugins.workflow:workflow-cps 2692.v76b), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-30945: 1.42% estimated exploitation activity in the next 30 days; percentile 72.90 (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.

Pipeline: Groovy Plugin allows pipelines to load Groovy source files. This is intended to be used to allow Global Shared Libraries to execute without sandbox protection. In Pipeline: Groovy Plugin 2689.v434009a31bf1 and earlier, any Groovy source files bundled with Jenkins core and plugins could be loaded this way and their methods executed. If a suitable Groovy source file is available on the classpath of Jenkins, sandbox protections can be bypassed. The Jenkins security team has been unable to identify any Groovy source files in Jenkins core or plugins that would allow attackers to execute dangerous code. While the severity of this issue is declared as High due to the potential impact, successful exploitation is considered very unlikely. Pipeline: Groovy Plugin 2692.v76b089ccd026 restricts which Groovy source files can be loaded in Pipelines. Groovy source files in public plugins intended to be executed in sandboxed pipelines have been identified and added to an allowlist. The new…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-2xvx-rw9p-xgfc

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-2022-30945

Advisory: Sandbox bypass vulnerability through implicitly allowlisted platform Groovy files in Jenkins Pipeline: Groovy Plugin
IDs: CVE-2022-30945, GHSA-2xvx-rw9p-xgfc
Record: https://patchnext.com/advisories/cve-2022-30945 (revision 1, source checked 26 Oct 2026, 16:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins.workflow:workflow-cps 2692.v76b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins.workflow:workflow-cps: affected <= 2689.v434009a; fixed in 2692.v76b

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins.workflow:workflow-cps: 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 org.jenkins-ci.plugins.workflow:workflow-cps.
- 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-2xvx-rw9p-xgfc (GitHub-reviewed advisory GHSA-2xvx-rw9p-xgfc lists affected ranges: Maven org.jenkins-ci.plugins.workflow:workflow-cps >=0 <=2689.v434009a)

Commands are suggestions: review each one before running it.

Loading voting…