CVE-2026-84651: Jenkins Jenkins vulnerability

Published Sep 2, 2026
·
Updated

In Jenkins 2.579 and earlier, LTS 2.568.2 and earlier, the REST API and CLI endpoints for updating agent configuration do not prevent a submitted configuration from overwriting a different agent by specifying that agent's name in the submitted XML document, allowing attackers with Agent/Configure permission on one agent to take over a different agent, gaining control of its configuration and obtaining access to its inbound agent secret and environment variables.

Affected Software

1 affected component
Jenkins Jenkins<=2.579, <=2.568.2

Event History

Sep 2, 2026
CVE Published
via MITRE·03:40 PM
Data Sourced
via MITRE·03:40 PM
Description
Data Sourced
via NVD·04:17 PM
Description

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs Agent/Configure permission on at least one Jenkins agent. They can then submit XML naming a different agent and overwrite that other agent's configuration.

2

What could an attacker obtain or control?

The attacker can take over another agent's configuration. This can expose that agent's inbound agent secret and environment variables.

3

Which Jenkins versions are affected?

Jenkins 2.579 and earlier, and Jenkins LTS 2.568.2 and earlier, are affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203