How severe is CVE-2018-1999002?

CVE-2018-1999002 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1999002?

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

How do I fix CVE-2018-1999002?

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

How do I detect CVE-2018-1999002 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-1999002 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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

Yes. There are 5 known exploit references for CVE-2018-1999002, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1999002?

CVE-2018-1999002 has an EPSS (Exploit Prediction Scoring System) score of 86.5%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

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

CVE-2018-1999002 was published on July 23, 2018 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

HIGH severity

CVE-2018-1999002 — jenkins-core

HIGHFix: jenkinsci/jenkins@29ca81d

CVE-2018-1999002 is a high-severity (CVSS 7.5) vulnerability in org.jenkins-ci.main:jenkins-core. 5 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Improper Input Validation in Jenkins

Also known asGHSA-qf38-f2fr-q4x9

Published

Jul 23, 2018

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

86.5%probability of exploitation in next 30 days

Very High Risk0.00%

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

2 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core

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 arbitrary file read vulnerability exists in Jenkins 2.132 and earlier, 2.121.1 and earlier in the Stapler web framework's org/kohsuke/stapler/Stapler.java that allows attackers to send crafted HTTP requests returning the contents of any file on the Jenkins master file system that the Jenkins master has access to.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.121.2`org.jenkins-ci.main:jenkins-core:2.121.2`
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 2.122&&< 2.132	2.132`org.jenkins-ci.main:jenkins-core:2.132`

Affected Products

2 products · 3 configurations

Application

jenkinsjenkins

≥ 2.122 && ≤ 2.132

range

Application

communications cloud native core automated test suiteoracle

1 version

1.9.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46453webappsjava

Jenkins Plugin Script Security 1.49/Declarative 1.3.4/Groovy 2.60 - Remote Code Execution

by wetw0rk · Feb 25, 2019

Exploit-DB Source

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.121.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1999002 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1999002 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

Weaponization

No Nuclei template or Metasploit module yet. 5 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

jenkins

6.6/10

Maintained10/10

Code-Review8/10

Branch-Protection3/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jul 23, 2018

First exploit

Feb 25, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2018-1999002

GHSA-qf38-f2fr-q4x9

References

Advisoryjenkins.io · 2018 07 18 Advisorynvd.nist.gov · CVE 2018 1999002 Fixoracle.com · cpuapr2022 Webgithub.com · 29ca81dd59c255ad633f1bd86cf1be40a5f02c64 Webgithub.com · 8e9679b08c36a2f0cf2a81855d5e04e2ed2ac2b3 Webexploit-db.com Packagegithub.com · jenkins Evidenceexploit-db.com

Related vulnerabilities

This CVE is high severity; 2 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-1999002 — 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

Frequently Asked Questions

Is CVE-2018-1999002 in your dependencies?