CVE-2026-84651

Description

A flaw was found in Jenkins. The system's application programming interface (API) and command-line interface (CLI) for managing agent configurations fail to properly validate the target agent. This vulnerability allows an attacker, who already has permissions to configure one agent, to overwrite the configuration of a different agent by manipulating the submitted data. Successful exploitation can lead to privilege escalation, granting the attacker control over the targeted agent's settings and access to sensitive information like its secret keys and environment variables.

Statement

A flaw was found in Jenkins. Privilege escalation is possible via agent configuration overwrite, allowing users with Agent/Configure permission to overwrite a different agent's configuration by manipulating the agent name in submitted XML. This issue affects Jenkins versions up to 2.579 (weekly) and up to 2.568.2 (LTS).

Mitigation

Update to Jenkins 2.580 (weekly) or Jenkins LTS 2.568.3 or later.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score8.1N/A6.3
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/ALow
Integrity ImpactHighN/ALow
Availability ImpactNoneN/ALow

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Understanding the Weakness (CWE)

Access Control

Technical Impact: Gain Privileges or Assume Identity

The attacker can gain access to otherwise unauthorized resources.

Integrity,Confidentiality,Other

Technical Impact: Modify Application Data; Modify Files or Directories; Read Application Data; Read Files or Directories; Other

Race conditions such as this kind may be employed to gain read or write access to resources not normally readable or writable by the user in question.

Integrity,Other

Technical Impact: Modify Application Data; Other

The resource in question, or other resources (through the corrupted one) may be changed in undesirable ways by a malicious user.

Non-Repudiation

Technical Impact: Hide Activities

If a file or other resource is written in this method, as opposed to a valid way, logging of the activity may not occur.

Non-Repudiation,Integrity

Technical Impact: Modify Files or Directories

In some cases it may be possible to delete files that a malicious user might not otherwise have access to -- such as log files.

Frequently Asked Questions

Want to get errata notifications? Sign up here.