Jenkins Groovy Plugin sandbox bypass vulnerability

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-2019-1003006: 1.60% estimated exploitation activity in the next 30 days; percentile 75.77 (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.

A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.0 and earlier in src/main/java/hudson/plugins/groovy/StringScriptSource.java that allows attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM. In version 2.1, the affected HTTP endpoint applies a safe Groovy compiler configuration preventing the use of unsafe AST transforming annotations.

Published by the source

13 May 2022, 01:15 UTC

Last modified by the source

30 Dec 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xfwj-2f34-32f5

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

# Patch Next advisory brief: CVE-2019-1003006

Advisory: Jenkins Groovy Plugin sandbox bypass vulnerability
IDs: CVE-2019-1003006, GHSA-xfwj-2f34-32f5
Record: https://patchnext.com/advisories/cve-2019-1003006 (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:groovy 2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:groovy: affected <= 2.0; fixed in 2.1

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:groovy: 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:groovy.
- 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-xfwj-2f34-32f5 (GitHub-reviewed advisory GHSA-xfwj-2f34-32f5 lists affected ranges: Maven org.jenkins-ci.plugins:groovy >=0 <=2.0)

Commands are suggestions: review each one before running it.