# CVE-2026-117615: Jenkins arbitrary file read via symlink following during item rename

Source: https://junglewise.ai/threats/cve-2026-117615-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-follows  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-28. Updated: 2026-10-28  
License: CC BY 4.0 with a link back

CVE-2026-117615 · Severity: info · Published 2026-10-28

Jenkins is an automation server that manages builds and jobs. When an administrator renames a job, Jenkins copies the job's directory on disk; in vulnerable versions, it incorrectly follows symbolic links during this copy operation. An attacker with permission to create and configure jobs can exploit this to read arbitrary files from the Jenkins server, potentially leading to credential theft or system compromise.

Technologies: [Jenkins](https://junglewise.ai/threats/technologies/jenkins). Vendors: [Jenkins](https://junglewise.ai/threats/vendors/jenkins).

## Quick answers

**Is CVE-2026-117615 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-117615 being exploited in the wild.

**How severe is CVE-2026-117615?** Informational severity, published 28 October 2026.

**Which products and versions are affected?** Jenkins 2.587 and earlier, LTS 2.580.1 and earlier.

**Is there a fix for CVE-2026-117615?** Yes: fixed in Jenkins 2.588, LTS 2.580.2. Until then: Jenkins 2.588 and LTS 2.580.2 no longer copy the directory of an item being renamed if it contains symbolic links, preventing exploitation of this vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-117615 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-117615?** Check whether you run Jenkins at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Jenkins 2.588, LTS 2.580.2

Jenkins 2.588 and LTS 2.580.2 no longer copy the directory of an item being renamed if it contains symbolic links, preventing exploitation of this vulnerability.

## Technical details

When Jenkins renames an item and cannot move its directory on the file system, it falls back to copying the directory. In Jenkins 2.587 and earlier, the copy operation follows symbolic links, allowing attackers with Item/Create and Item/Configure permissions to craft a job that exposes arbitrary files readable by the Jenkins process. The vulnerability exists in the item rename logic and can lead to disclosure of sensitive configuration files and credentials.

## Affected products

- Jenkins Jenkins 2.587 and earlier, LTS 2.580.1 and earlier

## Timeline

- 2026-10-28: advisory

## References

- [https://www.jenkins.io/security/advisory/2026-10-28/](https://www.jenkins.io/security/advisory/2026-10-28/)

## Related threats

- [Jenkins path traversal in file browser workspace disclosure](https://junglewise.ai/threats/cve-2026-117626-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-improperly)
- [Jenkins missing HTTP proxy permission check](https://junglewise.ai/threats/cve-2026-117625-a-missing-permission-check-in-jenkins-2-587-and-earlier-lts-2)
- [Jenkins deserialization filter bypass in XStream resolves-to attribute](https://junglewise.ai/threats/cve-2026-117624-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not)
- [Jenkins stored cross-site scripting in breadcrumb menu tooltips](https://junglewise.ai/threats/cve-2026-117623-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-does-not)
- [Jenkins agent XSS via Stapler HttpResponse exceptions](https://junglewise.ai/threats/cve-2026-117622-jenkins-2-587-and-earlier-lts-2-580-1-and-earlier-allows-agents)