Is CVE-2026-117617 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-117617 being exploited in the wild.

How severe is CVE-2026-117617?

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-117617?

Yes: fixed in Jenkins 2.588, LTS 2.580.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-117617 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-117617?

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.

CVE-2026-117617: Jenkins symbolic link in artifact extraction path traversal

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

Jenkins is a continuous integration and deployment automation platform used to build and test software. A flaw in how Jenkins processes extracted files allows attackers with job configuration permissions to write files to arbitrary locations on the Jenkins server by exploiting symbolic links in artifact archives. This could lead to server compromise or data manipulation.

Technologies: Jenkins. Vendors: Jenkins.

Quick answers

Is CVE-2026-117617 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-117617 being exploited in the wild.
How severe is CVE-2026-117617?: 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-117617?: Yes: fixed in Jenkins 2.588, LTS 2.580.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-117617 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-117617?: 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

Technical details

Jenkins validates symbolic links in extracted archive paths only before creating parent directories, but not immediately before writing files, allowing a time-of-check/time-of-use gap. An attacker with Item/Configure permission can craft an artifact archive with symbolic links that bypass validation and overwrite arbitrary files or directories on the controller filesystem. The vulnerability affects Jenkins 2.587 and earlier, with a patch available in 2.588.

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/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.