CVE-2026-117626
Description
A flaw was found in Jenkins. The file browser for workspaces and user content fails to properly validate file paths, resulting in a path traversal vulnerability. An authenticated attacker with read or workspace permissions can exploit this flaw by submitting crafted requests to obtain sensitive file metadata, such as file names, sizes, and modification timestamps from the Jenkins home directory, or discover the names of other jobs residing on the same agent.
Statement
This vulnerability is rated as Moderate because exploitation requires authenticated access with Overall/Read or Item/Workspace privileges and is limited to information disclosure. The flaw does not permit reading file contents, modifying data, or executing arbitrary code on the controller or agents. Instead, affected endpoints only expose filesystem metadata, such as directory structures, filenames, and timestamps, which limits the overall blast radius in standard deployments.
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.
