CVE-2026-117617 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 paren
Not scored
Published
Updated
Check this codebase for CVE-2026-117617 and fix it if it is affected.
What it is: CVE-2026-117617 is a vulnerability in Jenkins, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-117617 in the wild and no public exploit code.
Affected product: Jenkins. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-117617/ (Markdown: https://insights.sbomify.com/CVE-2026-117617/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-117617?
CVE-2026-117617 is a vulnerability in Jenkins, published on 28 Oct 2026.
Official description
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.
Which versions are affected by CVE-2026-117617?
How do I fix CVE-2026-117617?
No fix has been published for CVE-2026-117617 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-117617 being exploited?
There is no known exploitation of CVE-2026-117617 in the wild and no public exploit code.
Sources
Also known as GHSA-p6wg-qjmq-cvgh.