EUVD-2026-70125
GHSA-fc8j-cp67-6ww3
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Jenkins with low-privilege account
-
DeliverySend crafted Stapler POST to sandbox global-setting endpoint
-
ExploitBypass absent permission check (CWE-862)
-
ExecutionDisable 'Force sandbox globally' system setting
-
PersistAuthor or trigger Groovy pipeline without sandbox restrictions
-
ImpactExecute arbitrary OS commands on Jenkins controller
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid Jenkins account with at minimum Overall/Read access (PR:L per CVSS vector); anonymous or unauthenticated access cannot trigger this flaw. The Stapler HTTP endpoint must be network-reachable, which is typical for any Jenkins instance accessible to developers (AV:N). No special plugin configuration, non-default setting, or privileged role is required beyond possessing a low-privilege account and running a vulnerable plugin version (≤1412.v7737b_3405f86). The secondary impact - unrestricted Groovy execution - is further conditional on the attacker or a co-conspirator also holding pipeline or script execution rights, but the initial sandbox-disable action requires only basic authentication. |
| Impact | CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) captures only the immediate integrity impact of flipping a configuration toggle. The realistic threat model is more severe: once the sandbox is disabled globally, any Jenkins user with pipeline or shared-library execution rights gains effectively unrestricted Groovy execution, which is equivalent to OS command execution on the Jenkins controller and potentially on agents. Risk is highest in multi-tenant CI/CD environments where developer-level accounts are broadly distributed. EPSS data was not provided in input; KEV status is negative, and no public exploit code is known at time of analysis, placing exploitation probability in the speculative range. The combination of low-privilege requirement and network reachability (AV:N/PR:L) means a broad population of internal users can trigger the flaw without elevated credentials, making this a meaningful lateral-escalation stepping stone even if the 4.3 score does not convey urgency on its own. |
| Exploit ScenarioDerived | An authenticated Jenkins developer with a low-privilege account sends a crafted HTTP POST to the Stapler-routed configuration endpoint for the Script Security global sandbox setting. Because the permission check is absent, the request succeeds and sandbox enforcement is globally disabled. Any pipeline author on the system can now write a Jenkinsfile or shared-library Groovy script that calls arbitrary Java and OS APIs - for example, executing 'cmd.exe' or '/bin/bash' commands on the Jenkins controller - without any whitelist restriction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 02, 2026
Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier allows any low-privileged authenticated Jenkins user to disable the 'Force the use of the sandbox globally in the system' security control via a missing permission check exposed through Stapler data binding. The CVSS score of 4.3 reflects only the direct act of altering a setting, but the chained real-world risk is substantially higher: disabling global sandbox enforcement removes the primary defense against unrestricted Groovy execution, enabling subsequent RCE by any user with script authorship rights. No public exploit has been identified at time of analysis, and exploitation has not been confirmed by CISA KEV.
RemediationAI
Upgrade Jenkins Script Security Plugin to the fixed release identified in the Jenkins security advisory at https://www.jenkins.io/security/advisory/2026-09-02/#SECURITY-3986; the exact fixed version number is not specified in the available input data and must be confirmed directly from that advisory. As a compensating control prior to patching, restrict who holds Overall/Read or configuration-level permissions on the Jenkins controller to trusted personnel only, narrowing the population that can reach the vulnerable Stapler endpoint. Administrators should immediately audit the current state of the 'Force the use of the sandbox globally' setting in Manage Jenkins → Security and re-enable it if it has been silently disabled. Additionally, review script approval logs for any suspicious approvals that may have been submitted during a window when the sandbox was off.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Jenkins Script Security Plugin enforces a Groovy sandbox that whitelists permitted method calls and performs bytecode verification, preventing pipeline and job script authors from invoking dangerous Java APIs. The 'Force the use of the sandbox globally' system-level setting is the administrative override that ensures no operator can bypass this control. Jenkins's Stapler framework routes HTTP request parameters directly to Java object setters via reflection; when a setter controlling a sensitive security configuration lacks an authorization check, any authenticated caller can invoke it. CWE-862 (Missing Authorization) is the root cause - the method handling this setting does not verify that the caller holds the required Overall/Administer (or equivalent) Jenkins permission before accepting and persisting the change. CPE cpe:2.3:a:jenkins_project:jenkins_script_security_plugin:*:*:*:*:*:*:*:* confirms all versions of the plugin through 1412.v7737b_3405f86 are in scope.
Know when Jenkins Script Security Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Agrees with provided vector: PR:L (authenticated low-privilege user required), I:L (direct impact is toggling a setting), C:N and A:N since the act of disabling the sandbox does not itself exfiltrate data or crash services.
Primary rating from Vendor (jenkins).
CVSS VectorVendor: jenkins
Lifecycle Timeline
3DescriptionCVE.org
Jenkins Script Security Plugin 1412.v7737b_3405f86 and earlier does not enforce a permission check in the method that controls the "Force the use of the sandbox globally in the system" setting, allowing attackers to disable it through Stapler data binding.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Sandbox escape in the Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier lets an authenticated user who ho
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated att
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows authenticated users with
Sandbox escape leading to arbitrary code execution inside the Jenkins controller JVM affects Script Security Plugin 1415
Sandbox bypass in the Jenkins Script Security Plugin (1402.v94c9ce464861 and earlier) lets users who can supply sandboxe
Sandbox escape in the Jenkins Script Security Plugin (1415.v9a_f9b_3a_c253d and earlier) allows an authenticated Jenkins
Arbitrary code execution in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier: when a user with job-confi
Sandbox escape in Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier allows an authenticated Jenkins user
Sandbox escape in Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier allows users permitted to run sandboxed
Arbitrary code execution in the Jenkins Script Security Plugin (versions up to and including 1415.v9a_f9b_3a_c253d) lets
Improper use of the @DataBoundConstructor annotation in Jenkins Script Security Plugin versions ≤1412.v7737b_3405f86 ena
Jenkins Script Security Plugin versions up to and including 1399.ve6a_66547f6e1 expose classpath enumeration to any user
Exploit-DB