CVE-2026-117616
Description
A flaw was found in Jenkins. An authenticated attacker with Overall/Read permissions can exploit an unvalidated HTTP endpoint to achieve arbitrary code execution on the Jenkins controller. By supplying a crafted agent name, an attacker can load arbitrary configuration files from the controller file system and subsequently overwrite them when saving the agent.
Statement
Red Hat Product Security has rated this vulnerability as Important because an authenticated user with low-level access (Overall/Read privileges) can trigger path traversal to compromise system integrity and achieve remote code execution on the controller host. In typical Jenkins deployments, Overall/Read is commonly granted to standard developers and automated accounts, giving a broad pool of users the ability to target the vulnerable HTTP interface. While the attack requires valid credentials, the lack of administrative permission requirements and the potential for full controller takeover justify the Important rating.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
