CVE-2018-1999003: Incorrect Authorization in Jenkins
Summary
CVE-2018-1999003: Incorrect Authorization in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.121.2
>= 2.122, < 2.133
Fixed in 2.121.2 or 2.133, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. It is widely used in the software development industry due to its flexibility and extensive plugin ecosystem. The vulnerable package, org.jenkins-ci.main:jenkins-core, is a core component of Jenkins responsible for managing the build queue and scheduling jobs.
Vulnerability Detail
The vulnerability, identified as CVE-2018-1999003, is an improper authorization issue present in Jenkins versions 2.132 and earlier, as well as 2.121.1 and earlier. The vulnerability resides in the Queue.java file and allows attackers with Overall/Read permission to cancel queued builds. This means that an unauthorized user with this permission level can disrupt the build process and potentially cause delays or failures in the software development pipeline.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.121.22.121.2 -
>= 2.122, < 2.1332.133
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, administrators can review and adjust the permissions assigned to users with Overall/Read permission. By limiting this permission to trusted individuals or groups, the risk of unauthorized build cancellations can be mitigated. However, this workaround should only be considered temporary, and upgrading to the patched versions is strongly recommended.
Conclusion
In conclusion, the vulnerability in Jenkins allows attackers with Overall/Read permission to cancel queued builds, potentially disrupting the software development pipeline. It is crucial to upgrade to the patched versions mentioned and review permissions to mitigate the risk of unauthorized build cancellations. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
The vulnerability allows attackers with Overall/Read permission to cancel queued builds, potentially disrupting the software development pipeline and causing delays or failures in the build process.
Users of Jenkins versions 2.132 and earlier, as well as 2.121.1 and earlier, are affected by this vulnerability. Specifically, attackers with Overall/Read permission can exploit this vulnerability.
At the time of this report, there are no known public exploits targeting this vulnerability. However, it is important to promptly apply the recommended patches to prevent potential exploitation.
No, this vulnerability requires an attacker to have Overall/Read permission within the Jenkins instance. It cannot be exploited remotely without authenticated access to the Jenkins server.
Yes, the CVSS score for this vulnerability is 4.3, indicating a moderate severity level.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
