How severe is CVE-2018-1000997?

CVE-2018-1000997 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-1000997?

CVE-2018-1000997 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven), org.kohsuke.stapler:stapler-parent (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1000997?

Update org.jenkins-ci.main:jenkins-core to 2.138.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000997 is resolved across your whole dependency graph.

How do I detect CVE-2018-1000997 in my Maven dependencies?

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

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2018-1000997 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-1000997 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-2018-1000997?

CVE-2018-1000997 has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 88th 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-2018-1000997?

CVE-2018-1000997 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-1000997 published, and has it been updated?

CVE-2018-1000997 was published on January 23, 2019 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-2018-1000997 — jenkins-core

MEDIUMFix: jenkinsci/jenkins@fd5f5be

CVE-2018-1000997 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Improper Limitation of a Pathname to a Restricted Directory in Jenkins

Also known asGHSA-5hfp-964w-5vgm

Published

Jan 23, 2019

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% 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

3 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core☕org.kohsuke.stapler:stapler-parent

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

A path traversal vulnerability exists in the Stapler web framework used by Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/org/kohsuke/stapler/Facet.java, groovy/src/main/java/org/kohsuke/stapler/jelly/groovy/GroovyFacet.java, jelly/src/main/java/org/kohsuke/stapler/jelly/JellyFacet.java, jruby/src/main/java/org/kohsuke/stapler/jelly/jruby/JRubyFacet.java, jsp/src/main/java/org/kohsuke/stapler/jsp/JSPFacet.java that allows attackers to render routable objects using any view in Jenkins, exposing internal information about those objects not intended to be viewed, such as their toString() representation.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.138.2`org.jenkins-ci.main:jenkins-core:2.138.2`
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 2.140&&< 2.146	2.146`org.jenkins-ci.main:jenkins-core:2.146`
☕Maven	`org.kohsuke.stapler:stapler-parent`	all versions	1.250.2`org.kohsuke.stapler:stapler-parent:1.250.2`

Affected Products

1 product · 2 configurations

Application

jenkinsjenkins

≤ 2.145

range

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.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.138.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000997 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 HatModerate

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`atomic-enterprise-service-catalog-1:3.11.51-1.git.1671.2d16650.el7`	RHBA-2018:3743

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1000997 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

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

OpenSSF Scorecard

Package health score

jenkins

6.4/10

Code-Review6/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Jan 23, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2018-1000997

GHSA-5hfp-964w-5vgm

References

Advisoryjenkins.io · 2018 10 10 Advisorynvd.nist.gov · CVE 2018 1000997 Webgithub.com · fd5f5be0304c6bf1918892b81e2efb6b6d09c521 Webgithub.com · 0dfc28aa2102a59638484fc11c4c53b1dbb2baf0 Packagegithub.com · jenkins

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting jenkins-core are rated as high or higher (top: high).

CVE-2026-53436CVE-2026-53437CVE-2026-53440CVE-2026-53441CVE-2026-53439CVE-2026-53435CVE-2026-53442CVE-2026-53438

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2018-1000997 — jenkins-core

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-2018-1000997 in your dependencies?