CVE-2018-1000865: Improper Privilege Management in Jenkins Script Security Plugin
Summary
CVE-2018-1000865: Improper Privilege Management in Jenkins. Affects org.jenkins-ci.plugins:script-security versions < 1.48. Fixed in 1.48. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Jenkins Script Security Plugin is a component of the Jenkins automation server that allows users to execute arbitrary scripts securely. It provides a sandbox environment for executing Groovy scripts, ensuring that they do not have access to sensitive resources or perform malicious actions. However, a vulnerability in versions 1.47 and earlier of the plugin allows attackers with Job/Configure permission to bypass the sandbox and execute arbitrary code on the Jenkins master JVM. This vulnerability can be exploited if plugins using the Groovy sandbox are installed.
Vulnerability Detail
The vulnerability arises from an improper privilege management issue in the SandboxTransformer.java file of the Script Security Plugin. Attackers with Job/Configure permission can leverage this flaw to execute arbitrary code on the Jenkins master JVM. This can lead to unauthorized access, data breaches, and potential compromise of the entire Jenkins server. The vulnerability has a CVSS score of 8.8, indicating a high severity level.
How To Fix
Latest published version: 1436.v1082791135e4 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.48
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If immediate upgrading is not possible, a temporary workaround is to restrict Job/Configure permission to trusted users only. This can be done by modifying the Jenkins security settings and adjusting the permissions for the affected users. By limiting the number of users with Job/Configure permission, the risk of exploitation can be mitigated.
Conclusion
The vulnerability in the Jenkins Script Security Plugin allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM. To mitigate this risk, it is crucial to upgrade to version 1.48 or later of the plugin. Restricting Job/Configure permission to trusted users can also provide temporary protection. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:script-security →
FAQ
The vulnerability allows attackers with Job/Configure permission to execute arbitrary code on the Jenkins master JVM. This can lead to unauthorized access, data breaches, and potential compromise of the entire Jenkins server.
Versions 1.47 and earlier of the Script Security Plugin are affected by this vulnerability.
To fix this vulnerability, upgrade to version 1.48 or later of the Script Security Plugin.
A temporary workaround is to restrict Job/Configure permission to trusted users only.
The CVSS score of this vulnerability is 8.8, indicating a high severity level.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:script-security.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
