Skip to content

GHSA-c3jm-9vj7-5v66 CVE-2026-57280

Jenkins Script Security Plugin sandbox bypass vulnerability

High Maven
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.51%
Chance of exploitation in the next 30 days. Higher than 43.76% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-693 Protection Mechanism Failure
Fix
1402.1405.vc96e74964250
Upgrade org.jenkins-ci.plugins:script-security to this version or later

Description

Jenkins Script Security Plugin provides a sandbox feature that allows running user-provided scripts safely by intercepting and checking potentially unsafe operations.

Script Security Plugin 1402.v94c9ce464861 and earlier does not intercept the implicit type cast applied to each element of the iterated collection in a typed for loop (e.g. for (Type t in collection)), as this cast is performed during bytecode generation rather than in the transformed script AST.

This allows attackers able to provide sandboxed scripts to invoke constructors of arbitrary types without those invocations being checked by the sandbox, bypassing the sandbox protection. This can be used to execute arbitrary code on the Jenkins controller.

Script Security Plugin 1402.1405.vc96e74964250 updates the bundled groovy-sandbox library to a version that intercepts the implicit type cast applied to typed for loop elements, so those casts are checked by the sandbox.

Affected versions

Maven

PackageVulnerableFixed in
org.jenkins-ci.plugins:script-security
< 1402.1405.vc96e74964250
1402.1405.vc96e74964250

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.jenkins-ci.plugins:script-security Maven → 1402.1405.vc96e74964250

maven
<dependency><groupId>org.jenkins-ci.plugins</groupId><artifactId>script-security</artifactId><version>1402.1405.vc96e74964250</version></dependency>
gradle
implementation("org.jenkins-ci.plugins:script-security:1402.1405.vc96e74964250")

Severity breakdown

CVSS 3.1 8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2019-1003029
Sandbox bypass in Script Security Plugin
Critical Known exploited Also affects org.jenkins-ci.plugins:script-security
GHSA-cfj9-2vgr-hpxp
Jenkins Script Security Plugin has a script security bypass vulnerability
High Also affects org.jenkins-ci.plugins:script-security
GHSA-p334-gfhq-c7w6
Jenkins Script Security Plugin: Missing permission checks allow enumeration of pending and approved classpaths
Medium Also affects org.jenkins-ci.plugins:script-security
GHSA-jv82-75fh-23r7
Missing permission check in Jenkins Script Security Plugin
Medium Also affects org.jenkins-ci.plugins:script-security
GHSA-2g4q-9vm9-9fw4
Jenkins Script Security Plugin sandbox bypass vulnerability
High Also affects org.jenkins-ci.plugins:script-security
GHSA-v63g-v339-2673
Jenkins Script Security Plugin has sandbox bypass vulnerability involving crafted constructor bodies
Critical Also affects org.jenkins-ci.plugins:script-security
GHSA-76qj-9gwh-pvv3
Sandbox bypass in Jenkins Script Security Plugin
High Also affects org.jenkins-ci.plugins:script-security
GHSA-fv42-mx39-6fpw
Whole-script approval in Jenkins Script Security Plugin vulnerable to SHA-1 collisions
High Also affects org.jenkins-ci.plugins:script-security
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor