Jenkins 2.587 and earlier, LTS 2.580.1 and earlier improperly identifies file paths attempting path traversal in the
Source GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 19:44 UTC
Rated Medium 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
Until a fix is available, restrict permissions to minimize exposure, ensuring that only trusted users have Overall/Read and Item/Workspace permissions.
Description
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability in their file browser that improperly identifies file paths attempting path traversal. This flaw allows attackers with Overall/Read permission to access metadata such as names, sizes, and last modification times of files within the Jenkins home directory. Additionally, attackers with Item/Workspace permission can obtain the names of jobs that have a workspace on the same agent.