CVE-2018-1999002

CVE-2018-1999002 is a high-severity vulnerability in Jenkins with a CVSS 3.x base score of 7.5. Its EPSS exploit-prediction score of 87% places it in the 100th percentile, indicating an elevated likelihood of exploitation.

Key facts

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.

Frequently asked questions

What is CVE-2018-1999002?
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.
How severe is CVE-2018-1999002?
CVE-2018-1999002 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2018-1999002 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 87% (100th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1999002?
CVE-2018-1999002 primarily affects Jenkins. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2018-1999002?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-1999002 published?
CVE-2018-1999002 was published on 2018-07-23 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Jenkins

All CVEs affecting Jenkins →