GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins core: missing permission check exposes build parameters of jobs a user cannot otherwise see

CVE-2026-84656Control plane, storage & DevOpscurated

Impact

A user who holds Item/Read on any single job can read the build parameter names and values of jobs they have no access to at all. Build parameters routinely carry the things that make a CI controller worth attacking: registry paths, cluster and namespace targets, artifact locations, and values that teams treat as semi-secret because the job is supposed to be private. On a shared GPU fleet where one Jenkins controller drives training pipelines for several teams, this collapses the per-job access model into read-everything for anyone with a foothold in the controller. It is disclosure only - no write, no execution - but it is the reconnaissance step ahead of one. Affects Jenkins 2.579 and earlier and LTS 2.568.2 and earlier.

Who can reach it

Any authenticated Jenkins user holding Item/Read on at least one job. No access to the target jobs and no administrative rights are needed.

What to do

Upgrade the controller to the release named in the 2026-09-02 Jenkins advisory (SECURITY-4006); the record does not state the fixed version, so take it from the advisory rather than assuming one. Cost is a controller restart - the queue pauses, agents reconnect, and running builds are lost unless drained first. No GPU node impact. Until then, treat build parameters on that controller as readable by every authenticated user and move anything sensitive into the credentials store.

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.