GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Script Security Plugin: Groovy sandbox escape via AST annotation extensions member

CVE-2026-57281Control plane, storage & DevOpscurated

Impact

A user who can only submit sandboxed Groovy - the normal privilege level for anyone editing a Pipeline - can execute code outside the sandbox, as the Jenkins controller process user. On a fleet that builds and ships GPU workloads, the controller is usually the single richest credential store on the network: registry push tokens, kubeconfigs for the training clusters, SSH keys to bare-metal nodes, and signing material. Exploitation is conditional: it needs a suitable AST-transform-carrying script already on the classpath of the component evaluating the Groovy, which is why the vendor rates attack complexity high. Where it does apply, the result is full compromise of the CI control plane rather than of one job.

Who can reach it

Any authenticated Jenkins user permitted to define or run a sandboxed Groovy script (Pipeline job configuration, shared library, or similar). No administrator rights needed; the classpath precondition above must also hold.

What to do

Upgrade Script Security Plugin beyond 1402.v94c9ce464861 as directed by the Jenkins advisory. Red Hat OpenShift Developer Tools and Services users (4.12, 4.15-4.18) should take the corresponding RHSA errata instead. A plugin upgrade needs a Jenkins controller restart, so drain or quiesce in-flight builds first; agents and GPU nodes are unaffected and do not need rebooting.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.