GHSA-vxm7-6w3j-gm87
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Jenkins with Item/Configure permission
-
DeliveryOpen or create a Multijob project configuration
-
ExploitEmbed malicious Groovy payload in plugin scripting field
-
ExecutionSave configuration and trigger a build
-
PersistScript executes unsandboxed on Jenkins controller JVM
-
ImpactExfiltrate credentials and pivot to connected infrastructure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold Item/Create or Item/Configure permission in the Jenkins instance - permissions routinely granted to developers and pipeline owners, not limited to administrators. The Multijob Plugin version 669.v9d96a_d9c71b_0 or earlier must be installed and the plugin's Groovy scripting feature must be accessible within the project type. Unauthenticated exploitation is not possible; the attacker must have a valid Jenkins account with the specified permissions. Exploitation is further limited to Jenkins instances that have the Multijob Plugin installed; instances running only Jenkins core or other plugins are not affected by this CVE. The Jenkins user database (built-in) does not restrict usernames to ASCII, but access still requires authentication and the specific permission grants. |
| Impact | No CVSS vector or EPSS score was supplied for CVE-2026-70431 in the input data, so quantitative risk metrics are unavailable and the following assessment is entirely inferred from the vulnerability description. The required permissions - Item/Create or Item/Configure - are routinely granted to developers and CI/CD pipeline owners in Jenkins deployments; these are not administrative permissions, meaning the exploitable population within an organization is likely large. The impact of arbitrary code execution on the Jenkins controller JVM is critical in practice: Jenkins controllers typically hold credentials (SSH keys, API tokens, cloud credentials), have access to source repositories, and can deploy to production environments. Despite the absence of KEV or POC signals, the real-world risk to any organization running this plugin version with developer-accessible Item/Configure rights is high. The absence of CVSS data, EPSS, and POC confirmation means this cannot be quantitatively compared against other prioritized CVEs without vendor-supplied scoring from the Jenkins advisory at https://www.jenkins.io/security/advisory/2026-08-05/. |
| Exploit ScenarioDerived | A developer-level Jenkins user with Item/Configure permission opens a Multijob project's configuration page, locates the Groovy scripting field exposed by the plugin, and pastes a payload such as a reverse shell or credential-dumping script. Upon saving and triggering a build, the script executes unsandboxed on the Jenkins controller JVM, giving the attacker read access to all credentials stored in Jenkins, the ability to write files to the controller filesystem, and lateral movement capability to all connected agents and downstream deployment targets. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 05, 2026
Unsandboxed Groovy script execution in Jenkins Multijob Plugin 669.v9d96a_d9c71b_0 and earlier allows any attacker holding Item/Create or Item/Configure permission to run arbitrary code directly on the Jenkins controller JVM. The plugin exposes Groovy scripting capabilities that intentionally bypass the Script Security Plugin - the standard Jenkins mechanism for confining script execution to a restricted sandbox - meaning scripts execute with the full privileges of the Jenkins service account. The fix is available in Multijob Plugin 677.v7ffc23d6a_4c2; no public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog.
RemediationAI
Upgrade the Multijob Plugin to version 677.v7ffc23d6a_4c2 or later via the Jenkins plugin manager; this version integrates the plugin's Groovy scripting features with the Script Security Plugin, enforcing sandbox restrictions. The full advisory is at https://www.jenkins.io/security/advisory/2026-08-05/. If an immediate upgrade is not feasible, restrict Item/Create and Item/Configure permissions to only fully trusted administrators or service accounts - note this may break existing developer workflows and pipeline configurations. As a more aggressive compensating control, disable or uninstall the Multijob Plugin entirely; this eliminates the vulnerability surface but will break any pipelines relying on multi-phase job orchestration, requiring migration to alternative approaches such as Jenkins Pipelines with proper Groovy sandboxing. No workaround that preserves plugin functionality while blocking exploitation is apparent given the architectural nature of the bypass.
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
The Multijob Plugin provides multi-phase build orchestration within Jenkins, and it exposes Groovy scripting hooks for conditional logic and build step configuration. In the Jenkins security model, the Script Security Plugin acts as a sandboxing layer for Groovy scripts - restricting access to dangerous classes and methods unless an administrator has explicitly approved them via a script approval workflow. Plugins that implement Groovy evaluation without hooking into this framework bypass sandbox enforcement entirely, allowing scripts to call arbitrary Java and JVM APIs. This is a well-understood vulnerability class in the Jenkins ecosystem, structurally similar to CWE-693 (Protection Mechanism Failure) - the protection mechanism (Script Security sandbox) exists and is functional, but the plugin routes around it. The Jenkins controller JVM runs with the privileges of the OS user account hosting Jenkins, which in many deployments has broad filesystem access, credential store access, and internal network reachability. No CPE or CWE identifiers were included in the input data for this specific CVE.
Know when Jenkins 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:H/I:H/A:H
Network-accessible Jenkins UI, low-privilege Item/Configure grants trigger unsandboxed controller JVM code execution, constituting a scope change with full C/I/A impact.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Description PRE-NVD
Articles & Coverage 1
Executive ViewAI
Jenkins Multijob Plugin versions through 669 contain a critical remote code execution vulnerability that allows authenticated users with project configuration permissions to execute arbitrary code on the Jenkins controller by bypassing the standard security sandbox. This vulnerability threatens the integrity of CI/CD infrastructure and all systems that depend on Jenkins for automation. No public exploit identified at time of analysis.
Apply vendor patch to Multijob Plugin 677.v7ffc23d6a_4c2 or later. Until patching is complete, restrict Item/Create and Item/Configure permissions to only the minimum set of trusted administrators required for operations.
Threat Intelligence Overview
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/
The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary co
The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a
Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to ex
The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive j
The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and ea
A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.50 and earlier in src/main/java/org/jenkinsci/
A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in. Rated high severity (CVSS 8.
A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins
EUVD-2026-53525
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB