Jenkins Pipeline: Deprecated Groovy Libraries Plugin Protection Mechanism Failure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-25181: 1.60% estimated exploitation activity in the next 30 days; percentile 75.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Pipeline: Deprecated Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the same workspace directory for all checkouts of Pipeline libraries with the same name regardless of the SCM being used and the source of the library configuration. This allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM through crafted SCM contents, if a global Pipeline library already exists. Pipeline: Deprecated Groovy Libraries Plugin 561.vace0de3c2d69 uses distinct checkout directories per SCM for Pipeline libraries.

Published by the source

16 Feb 2022, 00:01 UTC

Last modified by the source

22 Dec 2023, 14:09 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7w2w-fwpf-9m4h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-25181

Advisory: Jenkins Pipeline: Deprecated Groovy Libraries Plugin Protection Mechanism Failure
IDs: CVE-2022-25181, GHSA-7w2w-fwpf-9m4h
Record: https://patchnext.com/advisories/cve-2022-25181 (revision 1, source checked 26 Oct 2026, 16:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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-global-lib 561.va_ce0de3c2d69. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins.workflow:workflow-cps-global-lib: affected <= 552.vd9cc05b8a2e1; fixed in 561.va_ce0de3c2d69

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins.workflow:workflow-cps-global-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 org.jenkins-ci.plugins.workflow:workflow-cps-global-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-7w2w-fwpf-9m4h (GitHub-reviewed advisory GHSA-7w2w-fwpf-9m4h lists affected ranges: Maven org.jenkins-ci.plugins.workflow:workflow-cps-global-lib >=0 <=552.vd9cc05b8a2e1)

Commands are suggestions: review each one before running it.