CVE-2026-84651 Overview
CVE-2026-84651 is a broken access control vulnerability in Jenkins affecting versions 2.579 and earlier, as well as LTS 2.568.2 and earlier. The REST API and CLI endpoints for updating agent configuration fail to prevent a submitted configuration from overwriting a different agent. An attacker specifies the target agent's name inside the submitted XML document to achieve this cross-agent overwrite.
Attackers with Agent/Configure permission on one agent can take over a different agent. Successful exploitation grants control over the victim agent's configuration and exposes its inbound agent secret and environment variables. The weakness is classified as [CWE-284: Improper Access Control].
Critical Impact
Authenticated attackers holding Agent/Configure on a single agent can pivot to control any other agent in the Jenkins controller, harvesting inbound agent secrets and environment variables that may contain credentials.
Affected Products
- Jenkins weekly releases 2.579 and earlier
- Jenkins LTS 2.568.2 and earlier
- Jenkins controllers exposing REST API and CLI agent configuration endpoints
Discovery Timeline
- 2026-09-02 - Jenkins publishes Security Advisory SECURITY-4025
- 2026-09-02 - CVE-2026-84651 published to NVD
- 2026-09-02 - Last updated in NVD database
Technical Details for CVE-2026-84651
Vulnerability Analysis
Jenkins exposes REST API and CLI endpoints that accept XML documents to update agent (node) configuration. The endpoints authenticate the caller and check whether the caller holds Agent/Configure permission on the agent identified in the request URL or command argument. The submitted XML also contains a <name> element identifying the target agent.
The vulnerability stems from Jenkins trusting the agent name embedded in the XML body rather than the agent selected by the permission check. When the two identifiers differ, Jenkins applies the configuration to the agent named in the XML. This overwrites a different agent than the one the caller is authorized to modify.
The impact extends beyond configuration tampering. Overwriting an agent's configuration allows the attacker to read back the inbound agent secret used to connect that agent to the controller. Environment variables stored on the agent, which frequently include build credentials and API tokens, become accessible to the attacker.
Root Cause
The root cause is a mismatch between the object used for authorization and the object modified by the operation. The permission check validates access against the URL-selected agent while the write operation targets the XML-named agent. See the Jenkins Security Advisory 2026-09-02 for the vendor's technical description.
Attack Vector
Exploitation requires network access to Jenkins and an authenticated account with Agent/Configure permission on at least one agent. The attacker submits a config.xml document over the REST API or CLI in which the <name> element references a different agent. The controller applies the submitted configuration to that other agent, allowing the attacker to inject launch commands, alter labels, and retrieve the victim agent's inbound secret.
Detection Methods for CVE-2026-84651
Indicators of Compromise
- REST API POST or PUT requests to /computer/<agentA>/config.xml where the response or subsequent state shows a different agent (agentB) has been modified.
- CLI invocations of update-node or equivalent from users who hold Agent/Configure on only a limited set of agents but appear to trigger configuration changes on other agents.
- Unexpected changes to agent launch method, labels, or environment variables in Jenkins audit logs.
- Reconnection of an inbound agent using a freshly rotated secret without an administrator-initiated action.
Detection Strategies
- Enable the Jenkins audit trail plugin and alert on agent configuration changes where the acting user lacks Administer and the modified agent differs from any agent the user owns.
- Compare the URL-selected agent name in access logs against the <name> value in the request body for config.xml submissions.
- Baseline agent configuration hashes and alert on drift outside of change windows.
Monitoring Recommendations
- Forward Jenkins controller logs and audit events to a centralized SIEM for correlation across users, endpoints, and agent identifiers.
- Monitor for bulk enumeration of /computer/ endpoints by non-administrative accounts, which often precedes targeted overwrite attempts.
- Track issuance and rotation events for inbound agent secrets and investigate rotations that lack a corresponding administrator action.
How to Mitigate CVE-2026-84651
Immediate Actions Required
- Upgrade Jenkins weekly to 2.580 or later, and Jenkins LTS to 2.568.3 or later, per the vendor advisory.
- Audit all accounts granted Agent/Configure and revoke the permission where it is not operationally required.
- Rotate inbound agent secrets and any credentials or tokens that were stored in agent environment variables on potentially exposed agents.
Patch Information
Jenkins has released fixed versions that enforce the authorization check against the agent identified in the XML body. Refer to the Jenkins Security Advisory 2026-09-02 for the full list of fixed versions and upgrade guidance.
Workarounds
- Restrict Agent/Configure to administrators until the controller is upgraded, as no configuration workaround fully addresses the flaw.
- Move sensitive build credentials from agent environment variables into the Jenkins credentials store, scoped to specific jobs and folders.
- Network-segment the Jenkins controller so that only trusted management hosts can reach the REST API and CLI endpoints.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
