GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Multijob Plugin: CSRF lets an attacker run code in the Jenkins controller JVM

CVE-2026-70432Control plane, storage & DevOpscurated

Impact

An endpoint in the plugin lacks CSRF protection, so an attacker who gets an authenticated Jenkins user to load a crafted page can execute arbitrary code in the controller JVM with that user's session. Unlike the plugin's sandbox-bypass issue, this needs no Jenkins account of the attacker's own - only a victim who is already logged in, which on an internal CI server is most of the engineering team during working hours. The consequence is the same: code in the controller, where the credentials that push images and drive the GPU cluster live. Only installations running the Multijob Plugin are affected.

Who can reach it

Anyone who can get an authenticated Jenkins user to visit a page they control. No Jenkins credentials of the attacker's own; the victim's existing session supplies the authentication.

What to do

The record names Multijob Plugin 669.v9d96a_d9c71b_0 and earlier and does not state a fixed release - read the Jenkins 2026-08-05 advisory (SECURITY-3823) before planning the change. Where no fix is available, remove the plugin, and keep the Jenkins UI off general-purpose browsing paths (SSO plus network restriction on the controller) so a crafted page cannot reach it. Plugin removal or update requires a controller JVM restart, aborting running builds.

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.