How severe is CVE-2019-1003001?

CVE-2019-1003001 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-1003001?

CVE-2019-1003001 affects the following packages: org.jenkins-ci.plugins.workflow:workflow-cps-parent (Maven), org.jenkins-ci.plugins:pipeline-model-definition (Maven), org.jenkins-ci.plugins:script-security (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-1003001?

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 CVE-2019-1003001 is resolved across your whole dependency graph.

How do I detect CVE-2019-1003001 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2019-1003001 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2019-1003001?

O3 pinpoints whether CVE-2019-1003001 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2019-1003001 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2019-1003001, including 2 documented proof-of-concept exploits on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-1003001?

CVE-2019-1003001 has an EPSS (Exploit Prediction Scoring System) score of 86.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

When was CVE-2019-1003001 published, and has it been updated?

CVE-2019-1003001 was published on January 22, 2019 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2019-1003001

HIGH

Jenkins Groovy Plugin sandbox bypass vulnerability

Also known asGHSA-6q78-6xvr-26fg

Published

Jan 22, 2019

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

86.2%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

Blast Radius

3 pkgs affected

☕org.jenkins-ci.plugins.workflow:workflow-cps-parent☕org.jenkins-ci.plugins:pipeline-model-definition☕org.jenkins-ci.plugins:script-security

Real-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

A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShellFactory.java that allows attackers with Overall/Read permission to provide a pipeline script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.workflow:workflow-cps-parent`	all versions	2.61.1
☕Maven	`org.jenkins-ci.plugins:pipeline-model-definition`	all versions	1.3.4.1
☕Maven	`org.jenkins-ci.plugins:script-security`	all versions	1.50

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46572remotejava✓ Verified

Jenkins 2.137 and Pipeline Groovy Plugin 2.61 - ACL Bypass and Metaprogramming Remote Code Execution (Metasploit)

by Metasploit · Mar 19, 2019

Exploit-DB Source

EDB-46427webappsjava✓ Verified

Jenkins Plugin Script Security < 1.50/Declarative < 1.3.4.1/Groovy < 2.61.1 - Remote Code Execution (PoC)

by orange · Feb 19, 2019

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins.workflow:workflow-cps-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 CVE-2019-1003001 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 pinpoints whether CVE-2019-1003001 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2019-1003001. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-1003001 in your dependencies?

O3 detects CVE-2019-1003001 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works