CVE-2026-92126
Description
A flaw was found in Jenkins Script Security Plugin. This vulnerability allows attackers with permission to define and run sandboxed scripts, such as Pipelines, to bypass the sandbox protection. The plugin fails to reject @Builder annotations that specify an arbitrary class in their builderStrategy member, leading to the instantiation of that class at compile time before sandbox rules are enforced. This can result in arbitrary code execution outside the sandbox if a suitable class exists on the classpath of the script evaluation component.
Statement
This vulnerability is rated as an Important severity flaw because bypassing sandbox restrictions allows unauthorized code execution in the Jenkins controller host environment, directly crossing trust boundaries. Exploitation requires that an attacker already possesses authenticated access to create or run Pipeline jobs or sandboxed scripts on the instance. Furthermore, successful execution depends on having an exploitable gadget class available on the controller classpath during script compilation, which limits immediate exposure and prevents a Critical rating.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Injected code can access resources that the attacker is directly prevented from accessing.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.
Non-Repudiation
Technical Impact: Hide Activities
Often the actions performed by injected control code are unlogged.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.