CVE-2026-117617: Jenkins Jenkins vulnerability

Published Oct 28, 2026
·
Updated

Jenkins 2.587 and earlier, LTS 2.580.1 and earlier checks for symbolic links in the path of an extracted file only before creating its parent directories, not immediately before writing it, and allows symbolic links in artifacts to replace existing files or empty directories, allowing attackers with Item/Configure permission to write files to arbitrary locations on the Jenkins controller file system.

Affected Software

1 affected component
Jenkins Jenkins<=2.587, <=2.580.1

Event History

Oct 28, 2026
CVE Published
via MITRE·04:48 PM
Data Sourced
via MITRE·04:48 PM
Description

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs Item/Configure permission in Jenkins. The issue can allow that attacker to write files to arbitrary locations on the Jenkins controller file system through crafted artifacts containing symbolic links.

2

Which Jenkins versions are affected?

Jenkins 2.587 and earlier are affected, as are Jenkins LTS 2.580.1 and earlier.

3

What filesystem targets can be altered?

The flaw allows symbolic links in artifacts to replace existing files or empty directories. The write can be directed to arbitrary locations on the Jenkins controller file system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203