How severe is CVE-2019-1003041?

CVE-2019-1003041 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-1003041?

CVE-2019-1003041 affects the following packages: org.jenkins-ci.plugins.workflow:workflow-cps (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-1003041?

Update org.jenkins-ci.plugins.workflow:workflow-cps to 2.65 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1003041 is resolved across your whole dependency graph.

How do I detect CVE-2019-1003041 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-1003041 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.

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

No public exploit code has been indexed for CVE-2019-1003041 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2019-1003041 has an EPSS (Exploit Prediction Scoring System) score of 3.4%, placing it in the 89th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-1003041?

CVE-2019-1003041 is classified as CWE-470 (CWE-470). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2019-1003041 was published on March 28, 2019 and was last updated on October 24, 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

Not in CISA KEV

CRITICAL severity

CVE-2019-1003041 — workflow-cps

CRITICALFix: jenkinsci/workflow-cps-plugin@2e5a67f

CVE-2019-1003041 is a critical-severity (CVSS 9.8) CWE-470 vulnerability in org.jenkins-ci.plugins.workflow:workflow-cps. A fix is available for org.jenkins-ci.plugins.workflow:workflow-cps — see the affected versions and patch details below.

Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin

Also known asGHSA-x74x-qf5j-35jh

Published

Mar 28, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins.workflow:workflow-cps

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 in Jenkins Pipeline: Groovy Plugin 2.64 and earlier allows attackers to invoke arbitrary constructors in sandboxed scripts.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.workflow:workflow-cps`	all versions	2.65`org.jenkins-ci.plugins.workflow:workflow-cps:2.65`

Affected Products

2 products · 2 configurations

Application

pipeline\jenkins

≤ 2.64

1 version

_groovy

Application

openshift container platformredhat

1 version

3.11

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, 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 to 2.65 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1003041 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.

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.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`jenkins-2-plugins-0:3.11.1553788831-1.el7`	RHSA-2019:1423

Frequently Asked Questions

A sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin 2.64 and earlier allows attackers to invoke arbitrary constructors in sandboxed scripts.

O3 Security · Impact-Aware SCA

Is CVE-2019-1003041 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-470CWE-470

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 28, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-1003041

GHSA-x74x-qf5j-35jh

References

Advisoryopenwall.com Advisorysecurityfocus.com Advisoryaccess.redhat.com · RHSA 2019:1423 Advisoryjenkins.io · 2019 03 25 Advisorynvd.nist.gov · CVE 2019 1003041 Webgithub.com · 2e5a67fde9baf25315fe692161b4e90d401da86c Packagegithub.com · workflow cps plugin

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs affecting workflow-cps is rated as high or higher (top: critical).

CVE-2024-52550CVE-2022-43404CVE-2022-43401CVE-2022-43402CVE-2020-2109CVE-2022-30945CVE-2018-1000866CVE-2017-1000096

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-1003041 — workflow-cps

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-1003041 in your dependencies?