Jenkins 2.587 and earlier, LTS 2.580.1 and earlier checks for symbolic links in the path of an extracted file only
Source GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 19:57 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins ProjectJenkins | Affected– | Fixed in– |
AI-suggested
The input does not provide information about available patches or vendor advisories. Until a fix is available, restrict Item/Configure permissions to trusted users only to reduce risk.
Description
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability in how symbolic links are checked during file extraction. The system only checks for symbolic links in the path before creating parent directories, not immediately before writing the file. This flaw allows attackers with Item/Configure permission to write files to arbitrary locations on the Jenkins controller file system by exploiting symbolic links in artifacts.