GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins OWASP ZAP Plugin: build operations run on the controller, giving Item/Configure users code execution

CVSS 8.8CVE-2026-57301Control plane, storage & DevOpscurated

Impact

The plugin performs its build operations on the Jenkins controller rather than on the assigned agent, so anyone holding Item/Configure can get arbitrary code execution in the controller process. The controller is the piece of CI that holds the fleet's deployment credentials, registry tokens and kubeconfigs, so this converts job-configuration access into control over what gets built and pushed onto GPU nodes. It is a privilege boundary failure, not a parsing bug: the agent isolation operators rely on to keep job code off the controller simply is not applied here.

Who can reach it

Network, authenticated: a Jenkins user with Item/Configure permission on any job that can use this plugin. No access to the controller host is needed.

What to do

No fixed version is listed in the advisory - 1.0.7 and earlier are affected. Uninstall or disable the OWASP ZAP Plugin, or remove Item/Configure from users who should not have controller-level code execution. The change is a plugin removal plus a controller restart; build agents and running workloads are untouched.

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.