CVE-2026-92129
Description
A flaw was found in Jenkins Script Security Plugin. Attackers with permissions to define and run sandboxed scripts, such as Pipelines, can bypass the sandbox protection. This is due to the plugin not checking calls from sandboxed scripts to methods added dynamically to a class at runtime. Successful exploitation allows for arbitrary code execution outside the sandbox.
Statement
This vulnerability is rated as having an Important severity because authenticated users with pipeline creation privileges can break out of the Groovy sandbox and execute arbitrary instructions on the Jenkins controller. Although exploitation requires existing access and job authoring permissions, escaping the security boundary compromises the entire controller process and adjacent infrastructure. Within Red Hat OpenShift Jenkins environments, this containment failure poses a direct risk to controller host resources and sensitive CI/CD credentials.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability,Other
Technical Impact: Execute Unauthorized Code or Commands; Alter Execution Logic
The attacker might be able to execute code that is not directly accessible to the attacker. Alternately, the attacker could call unexpected code in the wrong place or the wrong time, possibly modifying critical system state.
Availability,Other
Technical Impact: DoS: Crash, Exit, or Restart; Other
The attacker might be able to use reflection to call the wrong code, possibly with unexpected arguments that violate the API (CWE-227). This could cause the product to exit or hang.
Confidentiality
Technical Impact: Read Application Data
By causing the wrong code to be invoked, the attacker might be able to trigger a runtime error that leaks sensitive information in the error message, such as CWE-536.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
