Threats / Jenkins / CVE-2019-1003029
CVE-2019-1003029
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Jenkins Script Security Plugin vulnerability
Jenkins Script Security Plugin contains a sandbox bypass vulnerability that allows attackers to execute arbitrary code by circumventing the plugin's protection mechanisms.
Verdict
Today item — known-exploited.
An attacker can bypass the Script Security Plugin sandbox to execute arbitrary code within Jenkins. This vulnerability has been actively exploited in the wild and poses a critical risk to Jenkins deployments.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-25).
Probability (EPSS)
EPSS 0.74251 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Jenkins, Script Security Plugin. Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that the target runs Jenkins with the Script Security Plugin installed.
Business
Jenkins administrators rely on the Script Security Plugin to enforce code execution restrictions.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious script that exploits the sandbox bypass to execute arbitrary code.
Business
The sandbox protection mechanism fails to prevent unauthorized code execution.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute the script within the Jenkins environment to gain code execution privileges.
Business
Attackers gain the ability to run arbitrary commands with Jenkins process privileges.
4
Data at risk — exfiltration narrative 4
Attacker
I use this access to exfiltrate credentials, modify build pipelines, or establish persistence.
Business
Compromised Jenkins instances can be leveraged to attack downstream systems and supply chain targets.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05