GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins core: build CLI -s flag cancels other users' builds without the Item/Cancel permission

CVE-2026-84657Control plane, storage & DevOpscurated

Impact

The build CLI command does not check Item/Cancel when the -s flag is used to cancel a build it was waiting on, so a user holding only Item/Build can kill builds started by someone else. On a GPU fleet this is availability against the most expensive resource in the building: long training and benchmark jobs that have been queued behind scarce accelerators lose their hours of work and go back to the end of the queue, and repeated use is a cheap way for one tenant to starve another without ever holding a cancel permission. The impact is denial and disruption only - no data access, no execution - and Jenkins rates attack complexity high because it depends on the specific waiting-build flow. Affects Jenkins 2.579 and earlier and LTS 2.568.2 and earlier.

Who can reach it

An authenticated Jenkins user with Item/Build permission and CLI access to the controller. Item/Cancel is not required, which is the whole flaw.

What to do

Upgrade the controller to the release named in the 2026-09-02 Jenkins advisory (SECURITY-4015); the record does not state a fixed version, so take it from the advisory. Cost is a controller restart - queue pauses, agents reconnect, running builds lost unless drained. No GPU node reboot needed. Restricting CLI access on the controller narrows who can reach the affected command in the meantime.

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.