CVE-2026-92126 is a sandbox bypass in the Jenkins Script Security Plugin. Versions through 1415.v9a_f9b_3a_c253d let a user who can write sandboxed scripts or Pipelines run code outside the sandbox. NVD and Jenkins both rate it High (8.5). Update to 1422.v06869826dd9b_.
What's affected
The Jenkins advisory dated 16 September 2026 lists Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier as affected, tracked as SECURITY-3925. It names 1422.v06869826dd9b_ as the release that fixes it. The NVD record gives the same version.
The record lists CWE-470 (use of externally controlled input to select classes or code) and CWE-94 (code injection). The vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H. The advisory marks severity High, so the sources agree.
The advisory adds a qualifier that matters: the attack works in the rare case that a suitable class is present on the classpath of the component that evaluates the script. High complexity in the vector reflects this.
How to check if you're exposed
In Jenkins, open Manage Jenkins, then Plugins, then Installed plugins, and find Script Security. Compare its version with 1422.v06869826dd9b_. Anything at 1415.v9a_f9b_3a_c253d or earlier needs the update.
Also review who can define and run sandboxed scripts. That includes anyone who can create or edit Pipeline jobs, shared library code and similar script-bearing configuration. The advisory ties the exploit to attackers with that permission.
Paste a lockfile or SBOM into the free in-browser dependency scan to see whether this package is in your tree, including as a transitive dependency. Safeguard's reachability analysis can then show whether your code actually calls the affected path, which helps you order the work.
What to do now
- Update the Script Security Plugin to 1422.v06869826dd9b_ or later and restart Jenkins if prompted.
- Read the advisory's note on the change in behavior: sandboxed scripts can no longer refer to Groovy's builder strategies through a star import, but still can by fully qualified name or a single-class import. Test your Pipelines.
- Reduce the number of users who can create or change Pipelines.
- Check the same advisory for the other plugins it lists, since it covers several Jenkins components.
Why it matters
The sandbox in this plugin exists so that people who can write scripts cannot do everything the Jenkins controller can. The advisory explains that Groovy's @Builder annotation names a strategy class, and the compiler instantiates that class during compilation, before the sandbox is applied. A class named by the script author is therefore created outside the sandbox's checks.
The class of weakness is externally controlled selection of code. Any system that lets untrusted input choose which class gets loaded needs an allow list. The KEV flag in the record is false and the advisory does not mention exploitation.
Try it yourself
Pipeline definitions are code that needs review. This demo shows how gating a pull request catches risky changes before they reach the build server.
Click through it at your own pace, or open it full screen.
Quick check
Who can exploit this?
The advisory says attackers with permission to define and run sandboxed scripts, including Pipelines.
Will the update break scripts?
It may. The advisory notes a change in how builder strategies can be referenced, so test your Pipelines after upgrading.
Sources
Last reviewed: 18 October 2026.
