Threats / Jenkins / CVE-2019-1003030
CVE-2019-1003030
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Jenkins Matrix Project Plugin vulnerability
Jenkins Matrix Project Plugin contains a sandbox escape vulnerability enabling remote code execution. The flaw allows attackers to bypass security restrictions and execute arbitrary code on affected systems.
Verdict
Today item — known-exploited.
A sandbox escape in Jenkins Matrix Project Plugin permits remote code execution. The vulnerability is actively exploited in the wild, presenting significant risk to Jenkins deployments using this plugin.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
3 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-03-25).
Probability (EPSS)
EPSS 0.75961 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Jenkins, Matrix Project 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 Matrix Project Plugin fails to properly enforce sandbox restrictions on user-supplied input.
Business
Jenkins administrators face exposure of systems running the vulnerable plugin to unauthorized code execution.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious input that escapes the sandbox security model implemented by the plugin.
Business
Attackers gain execution context within the Jenkins process, compromising build integrity and system security.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with the privileges of the Jenkins process to establish persistence or pivot to other systems.
Business
Organizations experience data theft, lateral movement to connected infrastructure, and potential supply chain compromise through compromised builds.
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