CVE-2019-1003033: A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.1 and earlier in pom.xml, src/main/java/hudso

Q: How do I fix CVE-2019-1003033?

groovy: upgrade to newer than 2.1. Exact commands for each OS are on this page.

Q: Is CVE-2019-1003033 being exploited?

CVE-2019-1003033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-1003033 affect?

CVE-2019-1003033 affects groovy. Severity is high (CVSS 8.8). A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.1 and earlier in pom.xml, src/main/java/hudson/plugins/groovy/StringScriptSource.java that allows attackers with Overall/Read permission to execute arbitrary code on the Jenki

This month

HIGH 8.8UPGRADE

CVE-2019-1003033 is a high-severity flaw (CVSS 8.8) affecting groovy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.1 and earlier in pom.xml, src/main/java/hudson/plugins/groovy/StringScriptSource.java that allows attackers with Overall/Read permission to execute arbitrary code on the Jenkins master JVM.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.5% (top 15%)
CISA exploited list	No
Published	2019-03-08
Last modified	2026-06-17

Publisher (CNA): Jenkins Project · Vendor: jenkins

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-03-08 21:29 UTCPublished CVE record published
2026-06-17 02:09 UTCUpdated Record last modified

jenkins groovy UPGRADE

Affected: <= 2.1

Fixed in: newer than 2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy groovy || rpm -q groovy || groovy --version

2. UPGRADE to newer than 2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade groovy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade groovy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-1003033?

groovy: upgrade to newer than 2.1. Exact commands for each OS are on this page.

Is CVE-2019-1003033 being exploited?

CVE-2019-1003033 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-1003033 affect?

CVE-2019-1003033 affects groovy. Severity is high (CVSS 8.8). A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.1 and earlier in pom.xml, src/main/java/hudson/plugins/groovy/StringScriptSource.java that allows attackers with Overall/Read permission to execute arbitrary code on the Jenki

How urgent is CVE-2019-1003033?

Priority 52/100. High severity

Software pages

Java vulnerabilities · Jenkins vulnerabilities

Related CVEs

CVE-2020-17521 MEDIUM 5.5 UPGRADE MITIGATE Apache Groovy provides extension methods to aid with creating temporary directories
CVE-2019-1003006 HIGH 8.8 UPGRADE A sandbox bypass vulnerability exists in Jenkins Groovy Plugin 2.0 and earlier in src/main/java/hudson/plugins
CVE-2016-6814 CRITICAL 9.8 UPGRADE MITIGATE When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2
CVE-2015-3253 CRITICAL 9.8 DOWNGRADE DOWNGRADE The MethodClosure class in runtime/MethodClosure.java in Apache Groovy 1.7.0 through 2.4.3 allows remote attac

References

← Back to latest CVEs