GHSA-6q78-6xvr-26fg — workflow-cps-parent
HIGHFix: jenkinsci/pipeline-model-definition-plugin@6d7884dGHSA-6q78-6xvr-26fg is a high-severity (CVSS 8.8) remote code execution vulnerability in org.jenkins-ci.plugins.workflow:workflow-cps-parent. 5 public exploit references exist, so weaponization risk is real. A fix is available for org.jenkins-ci.plugins.workflow:workflow-cps-parent — see the affected versions and patch details below.
Jenkins Groovy Plugin sandbox bypass vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-6q78-6xvr-26fg plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jenkins-ci.plugins.workflow:workflow-cps-parent☕org.jenkins-ci.plugins:pipeline-model-definition☕org.jenkins-ci.plugins:script-securityReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Script Security sandbox protection could be circumvented during the script compilation phase by applying AST transforming annotations such as @Grab to source code elements.
Both the pipeline validation REST APIs and actual script/pipeline execution are affected.
This allowed users with Overall/Read permission, or able to control Jenkinsfile or sandboxed Pipeline shared library contents in SCM, to bypass the sandbox protection and execute arbitrary code on the Jenkins controller.
All known unsafe AST transformations in Groovy are now prohibited in sandboxed scripts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins.workflow:workflow-cps-parent | all versions | 2.61.1org.jenkins-ci.plugins.workflow:workflow-cps-parent:2.61.1 |
| ☕Maven | org.jenkins-ci.plugins:pipeline-model-definition | all versions | 1.3.4.1org.jenkins-ci.plugins:pipeline-model-definition:1.3.4.1 |
| ☕Maven | org.jenkins-ci.plugins:script-security | all versions | 1.50org.jenkins-ci.plugins:script-security:1.50 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Jenkins Plugin Script Security < 1.50/Declarative < 1.3.4.1/Groovy < 2.61.1 - Remote Code Execution (PoC)
by orange · Feb 19, 2019
Jenkins 2.137 and Pipeline Groovy Plugin 2.61 - ACL Bypass and Metaprogramming Remote Code Execution (Metasploit)
by Metasploit · Mar 19, 2019
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins.workflow:workflow-cps-parent to 2.61.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q78-6xvr-26fg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6q78-6xvr-26fg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6q78-6xvr-26fg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | atomic-enterprise-service-catalog-1:3.11.82-1.git.1673.133961e.el7 | RHBA-2019:0326 |
Frequently Asked Questions
Is GHSA-6q78-6xvr-26fg in your dependencies?
O3 Security finds GHSA-6q78-6xvr-26fg across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.