Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin

published 2018-02-09 8 y ago modified 2026-06-17 4 mo ago also GHSA-p3g4-9xfv-wq9v , EUVD-2022-4666

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.6%; EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits: 0; none known

Jenkins Pipeline: Supporting APIs Plugin 2.17 and earlier have an arbitrary code execution due to incomplete sandbox protection: Methods related to Java deserialization like readResolve implemented in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.

Patch / fix

fixed in 1

maven org.jenkins-ci.plugins.workflow:workflow-support 2.18

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000058 updated 2026-01-13 cvss 7.5

jenkins-plugin-workflow-support: Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin

Red Hat OpenShift Enterprise 3 jenkins-plugin-workflow-support
affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.57% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.5	AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins.workflow:workflow-support	<2.18	2.18

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

jenkins.io /security/advisory/2018-02-05/
vendor-advisory
securityfocus.com /bid/103034
vdb-entry, web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000058
advisory
jenkins.io /security/advisory/2018-02-05
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary