CVE-2026-117617
Description
A flaw was found in Jenkins. When extracting archived artifacts, Jenkins checks for symbolic links before creating parent directories rather than immediately before writing files, and allows symbolic links in artifacts to replace existing files or empty directories. An authenticated attacker with item configuration permissions can exploit this race condition by archiving artifacts concurrently to write files to arbitrary locations on the Jenkins controller file system, potentially resulting in arbitrary code execution.
Statement
This vulnerability is evaluated as an Important severity flaw because an authenticated attacker possessing job configuration permissions can escape the build directory and write arbitrary files to the controller file system, potentially achieving remote code execution. Exploitation requires non-default permissions (Item/Configure) and winning a race condition during concurrent artifact archiving operations. In standard deployments where item configuration privileges are restricted to trusted personnel, the immediate operational risk is substantially reduced.
Understanding the Weakness (CWE)
Integrity,Other
Technical Impact: Alter Execution Logic; Unexpected State
The attacker can gain access to otherwise unauthorized resources.
Integrity,Other
Technical Impact: Modify Application Data; Modify Files or Directories; Modify Memory; Other
Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.
Integrity,Other
Technical Impact: 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 in a valid way, logging of the activity may not occur.
Non-Repudiation,Other
Technical Impact: Other
In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.
Other
Technical Impact: Unexpected State
The product may perform invalid actions when the resource is in an unexpected state.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.