GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins: transient fields cannot be excluded from deserialization of submitted configuration

CVE-2026-84650Control plane, storage & DevOpscurated

Impact

Fields marked transient - which developers use precisely to keep runtime-only state out of persisted configuration - are still populated from user-submitted configuration, letting anyone who can push a configuration update dictate their values. The impact varies with how each transient field is used, so this is a class of exposure across core and plugins rather than one deterministic exploit, and it is the kind of primitive that other Jenkins bugs get chained onto. On a controller that deploys to GPU clusters, the accounts allowed to update job configuration are usually far broader than the accounts anyone intended to be able to influence controller internals. Affects Jenkins 2.579 and earlier, LTS 2.568.2 and earlier.

Who can reach it

Any authenticated user permitted to submit configuration updates on the controller. No user interaction required.

What to do

Upgrade the Jenkins controller per the advisory and restart it; the record does not name the fixed release. Short CI outage. Review which principals hold configure permission in the meantime, since that is the only gate.

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.