GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Pipeline: Build Step Plugin: downstream builds canceled without Item/Cancel permission

CVE-2026-84660Control plane, storage & DevOpscurated

Also covers 1 CVE

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

CVE-2026-84661

Impact

The plugin cancels downstream builds without checking that the triggering build's authentication holds Item/Cancel on the downstream job. The vendor split this across two ids in one advisory - CVE-2026-84660 for the build step and CVE-2026-84661 for waitForBuild with propagateAbort - but it is the same missing permission check in the same plugin with the same fix. The practical effect is a low-privilege pipeline author aborting jobs they have no authority over: on a shared CI that fronts a GPU fleet, that means killing another team's training or benchmark pipeline mid-run and wasting the accelerator hours it had already consumed. This is availability and integrity of the build queue, not code execution. Affects Pipeline: Build Step Plugin 599.v4b_67ea_11b_152 and earlier.

Who can reach it

An authenticated Jenkins user able to author or run a pipeline that invokes the build or waitForBuild step against a downstream job. No user interaction required.

What to do

Update the Pipeline: Build Step Plugin past 599.v4b_67ea_11b_152 and restart the controller; the record does not name the fixed release. One restart covers both ids. Short CI outage, no impact on running GPU workloads.

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.