How severe is CVE-2017-1000089?

CVE-2017-1000089 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-1000089?

CVE-2017-1000089 affects the following packages: org.jenkins-ci.plugins:pipeline-build-step (Maven). Ecosystems affected: Maven.

How do I fix CVE-2017-1000089?

Update org.jenkins-ci.plugins:pipeline-build-step to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000089 is resolved across your whole dependency graph.

How do I detect CVE-2017-1000089 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:pipeline-build-step, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000089 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2017-1000089 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000089 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-1000089?

CVE-2017-1000089 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-1000089?

CVE-2017-1000089 is classified as Incorrect Default Permissions (CWE-276). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-1000089 published, and has it been updated?

CVE-2017-1000089 was published on October 5, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2017-1000089 — pipeline-build-step

MEDIUM

CVE-2017-1000089 is a medium-severity (CVSS 5.3) Incorrect Default Permissions vulnerability in org.jenkins-ci.plugins:pipeline-build-step. A fix is available for org.jenkins-ci.plugins:pipeline-build-step — see the affected versions and patch details below.

Jenkins Build Step Plugin fails to check Item/Build permission

Also known asGHSA-8jx9-7j5m-79x4

Published

Oct 5, 2017

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:pipeline-build-step

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Builds in Jenkins are associated with an authentication that controls the permissions that the build has to interact with other elements in Jenkins. The Pipeline: Build Step Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:pipeline-build-step`	all versions	2.5.1`org.jenkins-ci.plugins:pipeline-build-step:2.5.1`

Affected Products

1 product · 1 configurations

Application

pipeline\jenkins

≤ 2.5

1 version

_build_step

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:pipeline-build-step, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:pipeline-build-step to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000089 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

This issue affects the versions of jenkins-plugin-pipeline-build-step as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification:…

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.6	`atomic-openshift-0:3.6.173.0.21-1.git.0.f95b0e7.el7`	RHBA-2017:2642

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-1000089 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CWE Classification

CWE-276Incorrect Default Permissions

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 5, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2017-1000089

GHSA-8jx9-7j5m-79x4

References

Advisoryjenkins.io · 2017 07 10 Advisorynvd.nist.gov · CVE 2017 1000089 Webjenkins.io · 2017 07 10

Related vulnerabilities

Also affects pipeline-build-step

This CVE is medium severity, in line with the other 3 CVEs affecting pipeline-build-step.

CVE-2023-25762CVE-2020-2118CVE-2022-25184

Same weakness: CWE-276

This CVE is medium severity; 5 of 5 other CVEs with CWE-276 are rated as high or higher (top: critical).

GHSA-763v-5pjm-fx36CVE-2026-77364CVE-2026-53657CVE-2026-52766CVE-2026-48790Browse all CWE-276

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-1000089 — pipeline-build-step

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2017-1000089 in your dependencies?