GHSA-fxm8-qw5f-4mmf
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Assessed for CVE-2026-70426: network-reachable via agent Remoting protocol, low complexity, Agent/Connect permission required (PR:L), scope change from agent to controller (S:C), full CIA impact on controller.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Description PRE-NVD
AnalysisAI
The August 2026 Jenkins security advisory discloses multiple severe vulnerabilities across Jenkins core (2.575/LTS 2.568.1 and earlier) and several plugins, with the most critical being a JEP-200 deserialization class filter bypass (CVE-2026-70426) enabling remote code execution on the Jenkins controller from agent processes, and a symlink-based path traversal in tar archive extraction (CVE-2026-70427) permitting arbitrary file writes that achieve controller RCE via init scripts or plugin deployment. Additional high-severity issues include a second path traversal via file parameter names (CVE-2026-70428), Unicode-based user identity impersonation (CVE-2026-70429), arbitrary type instantiation by privileged users (CVE-2026-70430), and unsandboxed Groovy RCE in the Multijob Plugin (CVE-2026-70431/70432). No active exploitation is confirmed at time of analysis, but the exploitability of agent-to-controller RCE paths in Jenkins is a well-understood and historically targeted vulnerability class warranting immediate remediation.
Technical ContextAI
Jenkins is a widely deployed open-source CI/CD automation server built on the Java platform. The most critical flaw (CVE-2026-70426) resides in the Remoting library (agent.jar/remoting.jar), which handles controller-agent communication via serialized Java objects. Jenkins enforces the JEP-200 class filter to prevent deserialization gadget attacks, but a fallback class resolution path in Remoting 3384.v60d89463d9e0 and earlier bypasses this filter entirely, exposing arbitrary Jenkins core classpath classes to deserialization exploitation. CVE-2026-70427 exploits tar/tar.gz extraction logic that fails to properly handle symbolic links with effectively empty names, enabling directory traversal to write files to sensitive controller locations such as JENKINS_HOME/init.groovy.d/ (auto-executed Groovy) or JENKINS_HOME/plugins/. CVE-2026-70428 reflects an improper path traversal detection failure in file parameter name handling (CWE-22 family). CVE-2026-70429 exploits a subtle inconsistency between Java's String#toLowerCase used for canonical ID creation and String#equalsIgnoreCase used for runtime comparisons: certain Unicode characters such as dotless-i ('ı') fold to different characters under each method, enabling identity collision without matching character sets. CVE-2026-70430 is an unsafe deserialization or reflection-based type instantiation issue in the project naming strategy subsystem. The Multijob Plugin CVEs (CVE-2026-70431/70432) involve Groovy scripting execution paths that do not integrate with the Jenkins Script Security Plugin sandbox, permitting unsandboxed JVM-level code execution.
RemediationAI
Upgrade Jenkins core to weekly release 2.576 or LTS 2.568.2 immediately to resolve CVE-2026-70426 through CVE-2026-70430; this is the primary and only confirmed fix for the core vulnerabilities. For plugin fixes, upgrade Multijob Plugin to 677.v7ffc23d6a_4c2, HCL AppScan Plugin to 1.8.4, External Workspace Manager Plugin to 1.4.2, SCM-Manager Plugin to 1.12.1, and Webhook Secret Credentials Provider Plugin to 32.v09c9b_522f0a_8. The eleven plugins with unresolved vulnerabilities have no available patches as of this advisory; mitigations include disabling these plugins entirely until fixes are released, and restricting Item/Configure, Item/Create, and Overall/Read permissions to fully trusted users only - noting that overly broad permission restriction may impair build pipeline functionality. For CVE-2026-70426 specifically, if immediate Jenkins core upgrade is not operationally feasible, restricting Agent/Connect permission to only explicitly trusted and controlled principals and auditing all connected agents for legitimacy reduces the attack surface, though this is not a complete mitigation. Full advisory and remediation guidance is available at https://www.jenkins.io/security/advisory/2026-08-05/.
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
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-53540