Technical impact
The vulnerability allows an attacker with overall/read permission on a Jenkins instance to load any config.xml file from the controller file system by exploiting an HTTP endpoint that does not validate the agent name. This omission lets the attacker provide an arbitrary agents’ configuration or overwrite existing config.xml files during a save operation, thereby enabling the execution of attacker-supplied code on the Jenkins controller. The likely attack vector is a web request to the vulnerable agent‑loading endpoint, where the attacker supplies a crafted agent name. Because the request is authenticated only with overall/read rights, the attacker requires a user account that has at least read access to the controller. The impact is critical: a successful exploit results in full code execution on the Jenkins controller, compromising confidentiality, integrity, and availability of the entire CI/CD environment.
Affected Systems
This flaw affects the Jenkins Project’s Jenkins product. Specifically, Jenkins releases 2.587 and all earlier versions, as well as Long‑Term Support releases 2.580.1 and all earlier LTS versions are vulnerable.
Risk and Exploitability
The CVSS score is 8.8, indicating a high severity, with an EPSS score of < 1%. The vulnerability is not listed in the CISA KEV catalog, suggesting that public exploitation is not widely reported. Nonetheless, the requirement of only Overall/Read permission means that attackers with access to the Jenkins web console, or who can create a user with read rights, can potentially exploit the flaw. The risk is high for any organization that runs unpatched Jenkins versions.