EUVD-2026-38761
GHSA-cfj9-2vgr-hpxp
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as script-authoring user
-
DeliveryCraft Groovy with AST annotation extensions member
-
ExploitReference gadget transform class on classpath
-
ExecutionSubmit script for sandboxed evaluation
-
PersistTransformation runs outside sandbox
-
ImpactExecute arbitrary code on controller
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires an account authorized to submit and run sandboxed Groovy scripts (PR:L) - for example a user with permission to define Pipeline jobs or shared-library scripts on the controller; fully unauthenticated exploitation is not possible. The script must carry a Groovy AST transformation annotation with an 'extensions' member, and - critically - a suitable transformation class must already exist on the classpath of the component evaluating the script; without such a gadget class present, the bypass does not fire (this is the AC:H limiting factor). No user interaction from an admin is needed. Administrators who can already run non-sandboxed scripts gain no privilege from this, so the meaningful exposure is limited to lower-privileged script authors on affected plugin versions. |
| Impact | Signals are internally consistent and point to a real-but-conditional risk rather than an urgent mass-exploitation event. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.5 High) reflects that exploitation is network-reachable but requires an authenticated user with script-running privileges (PR:L) and hinges on a suitable gadget class being present on the classpath (AC:H). SSVC agrees: Exploitation 'none', Automatable 'no', but Technical Impact 'total' - meaning full compromise if achieved, yet not trivially weaponizable at scale. EPSS is low (0.39%, 30th percentile) and there is no KEV listing and no known POC, so this is not currently under active or widespread exploitation. The chief mitigating reality is that anyone who can already run non-sandboxed scripts (Jenkins admins) gains nothing; the risk is elevation from a restricted script-author role to full controller code execution. Note a minor tagging discrepancy: the intelligence tags label this 'Information Disclosure', but the description and impact metrics describe full code execution - treat it as sandbox-escape RCE, not mere disclosure. |
| Exploit ScenarioDerived | An authenticated Jenkins user who is allowed to submit sandboxed Groovy (for example via a Pipeline job or a shared-library script) crafts a script containing an AST transformation annotation whose 'extensions' member references a transformation class already present on the controller's classpath. When the plugin compiles the script, the referenced transformation executes outside the sandbox, giving the attacker code execution with the controller's privileges. No public POC is known, and the attack depends on a suitable gadget class being available, giving it high attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Sandbox escape in Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier allows users permitted to run sandboxed Groovy scripts to execute arbitrary code outside the sandbox. The plugin fails to reject Groovy AST transformation annotations that carry an 'extensions' member, so an attacker can point that member at a suitable class already on the evaluating component's classpath and have it run outside sandbox restrictions. No public exploit identified at time of analysis, and SSVC exploitation status is 'none'; EPSS is low at 0.39%.
RemediationAI
Upgrade the Jenkins Script Security Plugin to the fixed release published with advisory SECURITY-3793 (https://www.jenkins.io/security/advisory/2026-06-24/#SECURITY-3793); the advisory is the authoritative source for the exact patched version, which is a version later than 1402.v94c9ce464861 (verify the precise build number in the advisory before deploying, as it is not independently confirmed in this dataset). As an interim compensating control until patching, restrict who can author or run Groovy scripts by tightening the 'Overall/Administer' and script approval permissions so that only trusted administrators can submit sandboxed scripts, and require manual script approval rather than allowing arbitrary sandboxed submissions - the trade-off is added friction for legitimate pipeline authors. Reducing the number of unnecessary plugins on the controller's classpath also shrinks the pool of usable gadget classes, at the cost of removing functionality. Avoid exposing the Jenkins controller directly to untrusted networks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The plugin implements the Groovy sandbox that underpins Jenkins Pipeline, Job DSL, and other Script Console-adjacent features, using a Groovy compiler transformation to intercept and vet method calls. Groovy supports local AST (Abstract Syntax Tree) transformation annotations, and such annotations can specify an 'extensions' member naming additional transformation classes to load and execute at compile time. Because the plugin did not reject annotations bearing this 'extensions' member, an attacker-supplied script could reference a transformation class present on the classpath, causing code to run during compilation before or outside the sandbox's runtime interception. This is a classic CWE-693 Protection Mechanism Failure: the sandbox exists but a bypass path around it was left open. The single affected component is cpe:2.3:a:jenkins_project:jenkins_script_security_plugin, which is a dependency of dozens of other Jenkins plugins.
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable but needs an authenticated script author (PR:L) and a suitable classpath gadget (AC:H); successful escape yields full controller code execution (C/I/A:H).
Primary rating from Vendor (jenkins).
CVSS VectorVendor: jenkins
Lifecycle Timeline
2DescriptionCVE.org
Jenkins Script Security Plugin 1402.v94c9ce464861 and earlier does not reject Groovy AST transformation annotations carrying an extensions member, allowing attackers able to run sandboxed Groovy scripts to execute code outside the sandbox if a suitable script is present on the classpath of the component that evaluates the script.
Blast Radius
ecosystem impact- 4 maven packages depend on org.jenkins-ci.plugins:script-security (4 direct, 0 indirect)
Ecosystem-wide dependent count for version 1402.1405.vc96e74964250.
Articles & Coverage 2
Executive ViewAI
Jenkins Script Security Plugin versions through 1402.v94c9ce464861 contain a sandbox escape that allows privileged Jenkins users to execute arbitrary code with full system privileges, directly compromising CI/CD pipeline integrity and supply chain security. Malicious or compromised accounts could alter deployments, extract credentials, and access source repositories, representing a critical insider threat vector.
Until a patch is available, enforce least-privilege access to Script Security Plugin permissions; require multi-factor authentication for all users with script execution rights; implement network segmentation isolating Jenkins infrastructure from direct production system access; maintain detailed immutable logs of all script execution with real-time alerting for anomalous activity; conduct quarterly access reviews and revoke unused script execution privileges; disable sandboxed Groovy scripting if not mission-critical.
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
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
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 1412.v7737b_3405f86 and earlier allows any low-privileged authenticated Jenkins user to d
Jenkins Script Security Plugin versions up to and including 1399.ve6a_66547f6e1 expose classpath enumeration to any user
Exploit-DB