GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Credentials Binding Plugin: unsanitized credential file names write files anywhere on the node

CVSS 7.5CVE-2026-42520Control plane, storage & DevOpscurated

Impact

A user who can supply file or zip credentials to a job can set a file name containing path traversal, causing Jenkins to write attacker-chosen content to an arbitrary path on the node running the build. Where a low-privileged user may configure such credentials for a job on the built-in node, that becomes code execution as the Jenkins controller - which in a GPU fleet usually holds the keys to image registries, node provisioning and cluster credentials. A compromised build controller is a straight path to the whole cluster, and rebuilding it is far more expensive than patching it.

Who can reach it

Authenticated Jenkins user with permission to provide credentials to a job. Attack complexity is rated high, reflecting the configuration conditions that must hold (jobs running on the built-in node with low-privileged credential configuration).

What to do

Update the Credentials Binding Plugin past 719.v80e905ef14eb_ to the version named in the Jenkins advisory of 2026-04-29 (SECURITY-3672) and restart the controller. In the meantime, stop running jobs on the built-in node and restrict who may configure file and zip credentials. Plugin update plus controller restart only - no node maintenance.

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.