GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins External Workspace Manager: path traversal in exwsAllocate reads any controller file

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

Impact

Version 1.3.2 and earlier accept path traversal sequences in the custom workspace path given to the exwsAllocate Pipeline step, so a user who can configure a job reads arbitrary files on the Jenkins controller filesystem - which the advisory notes can lead to remote code execution. The controller filesystem is where Jenkins keeps credentials stores, SSH keys and agent secrets, so this is a route from job-configure rights to the keys that drive the build and deploy path for a fleet. For operators who use external workspaces to stage large datasets or model artifacts for GPU builds, the affected step is in the normal pipeline path rather than an obscure feature.

Who can reach it

Any authenticated Jenkins user with Item/Configure permission on a job that can invoke the exwsAllocate step. No administrator rights needed.

What to do

Update the External Workspace Manager Plugin past 1.3.2 following the 2026-06-24 Jenkins advisory and restart the controller. If no fixed release is available for your line, remove or disable the plugin and withdraw Item/Configure from users who do not need it; rotate credentials held on the controller if you suspect the step was abused.

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.