CVE-2019-1003030

CRITICALNVD 9.99.9—
EchelonGraph scoreHIGH confidence

Score elevated to 9.9 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.9 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.9EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 97%CVSS: 9.9Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able to control pipeline scripts to execute arbitrary code on the Jenkins master JVM.

CVSS v3
9.9
EG Score
9.9CRITICALhigh confidence
EG Risk
85
EG Risk 85/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
97%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 8, 2019

Last Modified

October 24, 2025

Advisory Details (5)

Auto-updated Oct 5, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: redhat, cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1003030
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2019:0739
generic🔴 Active Exploitation

CVE-2019-1003029 - PSIRT.COM

http://www.securityfocus.com/bid/107476

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjenkins-2-plugins-0:3.11.1552336312-1.el72019-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.jenkins-ci.plugins.workflow:workflow-cps0.1-beta-1 ... 2.9 (129 versions)
  • every version up to 2.64: fixed in 2.64
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 50× in last 7d / 218× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 997 total refreshes for this CVE.

  1. 2026-10-09 21:37 UTCVendor advisory
  2. 2026-10-09 17:52 UTCVendor advisory
  3. 2026-10-09 14:07 UTCVendor advisory
  4. 2026-10-09 10:22 UTCVendor advisory
  5. 2026-10-09 06:37 UTCVendor advisory
  6. 2026-10-09 02:51 UTCVendor advisory
  7. 2026-10-08 23:06 UTCVendor advisory
  8. 2026-10-08 19:21 UTCVendor advisory
  9. 2026-10-08 15:36 UTCVendor advisory
  10. 2026-10-08 11:51 UTCVendor advisory
  11. 2026-10-08 08:05 UTCVendor advisory
  12. 2026-10-08 04:20 UTCVendor advisory
  13. 2026-10-08 00:35 UTCEG score recompute
  14. 2026-10-08 00:35 UTCVendor advisory
  15. 2026-10-07 23:42 UTCEPSS rescore
  16. 2026-10-07 20:50 UTCVendor advisory
  17. 2026-10-07 17:05 UTCVendor advisory
  18. 2026-10-07 13:16 UTCVendor advisory
  19. 2026-10-07 09:31 UTCVendor advisory
  20. 2026-10-07 05:45 UTCVendor advisory
  21. 2026-10-07 02:00 UTCVendor advisory
  22. 2026-10-06 22:14 UTCVendor advisory
  23. 2026-10-06 18:29 UTCVendor advisory
  24. 2026-10-06 14:44 UTCVendor advisory
  25. 2026-10-06 10:59 UTCVendor advisory
Show 75 more
  1. 2026-10-06 07:14 UTCVendor advisory
  2. 2026-10-06 03:29 UTCVendor advisory
  3. 2026-10-06 03:29 UTCVendor advisory
  4. 2026-10-06 03:28 UTCVendor advisory
  5. 2026-10-06 03:28 UTCVendor advisory
  6. 2026-10-05 23:43 UTCVendor advisory
  7. 2026-10-05 19:57 UTCVendor advisory
  8. 2026-10-05 16:13 UTCVendor advisory
  9. 2026-10-05 12:28 UTCVendor advisory
  10. 2026-10-05 08:44 UTCVendor advisory
  11. 2026-10-05 04:59 UTCVendor advisory
  12. 2026-10-05 01:14 UTCVendor advisory
  13. 2026-10-04 21:29 UTCVendor advisory
  14. 2026-10-04 17:44 UTCVendor advisory
  15. 2026-10-04 13:58 UTCVendor advisory
  16. 2026-10-04 10:13 UTCVendor advisory
  17. 2026-10-04 06:27 UTCVendor advisory
  18. 2026-10-04 02:43 UTCVendor advisory
  19. 2026-10-03 22:58 UTCVendor advisory
  20. 2026-10-03 19:11 UTCVendor advisory
  21. 2026-10-03 15:27 UTCVendor advisory
  22. 2026-10-03 11:40 UTCVendor advisory
  23. 2026-10-03 07:55 UTCVendor advisory
  24. 2026-10-03 04:08 UTCVendor advisory
  25. 2026-10-03 00:23 UTCVendor advisory
  26. 2026-10-02 20:39 UTCVendor advisory
  27. 2026-10-02 16:52 UTCVendor advisory
  28. 2026-10-02 13:07 UTCVendor advisory
  29. 2026-10-02 09:20 UTCVendor advisory
  30. 2026-10-02 05:35 UTCVendor advisory
  31. 2026-10-02 01:48 UTCVendor advisory
  32. 2026-10-01 22:01 UTCVendor advisory
  33. 2026-10-01 18:12 UTCVendor advisory
  34. 2026-10-01 14:25 UTCVendor advisory
  35. 2026-10-01 10:40 UTCVendor advisory
  36. 2026-10-01 06:53 UTCVendor advisory
  37. 2026-10-01 03:08 UTCVendor advisory
  38. 2026-09-30 23:23 UTCVendor advisory
  39. 2026-09-30 19:37 UTCVendor advisory
  40. 2026-09-30 15:52 UTCEG score recompute
  41. 2026-09-30 15:52 UTCVendor advisory
  42. 2026-09-30 14:59 UTCEPSS rescore
  43. 2026-09-30 12:07 UTCVendor advisory
  44. 2026-09-30 08:22 UTCVendor advisory
  45. 2026-09-30 04:37 UTCVendor advisory
  46. 2026-09-30 00:48 UTCVendor advisory
  47. 2026-09-29 21:03 UTCVendor advisory
  48. 2026-09-29 17:15 UTCVendor advisory
  49. 2026-09-29 13:28 UTCVendor advisory
  50. 2026-09-29 09:43 UTCVendor advisory
  51. 2026-09-29 05:58 UTCVendor advisory
  52. 2026-09-29 02:14 UTCVendor advisory
  53. 2026-09-28 22:28 UTCEG score recompute
  54. 2026-09-28 22:28 UTCVendor advisory
  55. 2026-09-28 18:43 UTCVendor advisory
  56. 2026-09-28 14:58 UTCVendor advisory
  57. 2026-09-28 11:13 UTCVendor advisory
  58. 2026-09-28 07:28 UTCVendor advisory
  59. 2026-09-28 03:43 UTCVendor advisory
  60. 2026-09-27 23:58 UTCVendor advisory
  61. 2026-09-27 21:51 UTCCISA KEV update
  62. 2026-09-27 20:13 UTCVendor advisory
  63. 2026-09-27 16:28 UTCVendor advisory
  64. 2026-09-27 12:43 UTCVendor advisory
  65. 2026-09-27 08:58 UTCVendor advisory
  66. 2026-09-27 05:14 UTCVendor advisory
  67. 2026-09-27 01:29 UTCVendor advisory
  68. 2026-09-26 21:39 UTCVendor advisory
  69. 2026-09-26 17:55 UTCVendor advisory
  70. 2026-09-26 14:10 UTCVendor advisory
  71. 2026-09-26 10:24 UTCVendor advisory
  72. 2026-09-26 06:38 UTCVendor advisory
  73. 2026-09-26 02:53 UTCVendor advisory
  74. 2026-09-25 23:08 UTCVendor advisory
  75. 2026-09-25 19:35 UTCCISA KEV update

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48904
    First seen Oct 19, 2020

    Jenkins 2.63 - Sandbox bypass in pipeline: Groovy plug-in

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-1003030.yaml
    First seen Jan 1, 2019

    Jenkins Pipeline Groovy Plugin <=2.63 - Insecure Deserialization

    Open source ↗

Frequently asked(6)

What is CVE-2019-1003030?
CVE-2019-1003030 is a critical vulnerability published on March 8, 2019. A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java that allows attackers able to control pipeline scripts to execute arbitrary code on the Jenkins master JVM.
When was CVE-2019-1003030 disclosed?
CVE-2019-1003030 was first published on March 8, 2019, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-1003030 actively exploited?
Yes. CISA added CVE-2019-1003030 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting Jenkins Matrix Project Plugin. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-1003030?
CVE-2019-1003030 has a CVSS v3 base score of 9.9 (NVD).
Which products are affected by CVE-2019-1003030?
CVE-2019-1003030 affects Jenkins Matrix Project Plugin. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-1003030?
A fix for CVE-2019-1003030 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-1003030

Explore →

Is Your Infrastructure Affected by CVE-2019-1003030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.