Jenkins 2.587 and earlier, LTS 2.580.1 and earlier improperly identifies file paths attempting path traversal in the
Affects jenkinsSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.588.0 or 2.580.2 when convenient.
Data as of 17 Nov 2026, 16:50 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 2.588.0, 2.580.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 16 Nov 2026.
What to do
Upgrade jenkins to 2.588.0 or 2.580.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamijenkinspkg:bitnami/jenkinsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Jenkins to version 2.588.0 or later, or LTS 2.580.2 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.
Description
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where file paths attempting path traversal are improperly identified in the file browser for workspaces and $JENKINS_HOME/userContent/. This allows attackers with Overall/Read permission to obtain metadata such as names, sizes, and last modification times of files within $JENKINS_HOME. Additionally, attackers with Item/Workspace permission can obtain the names of jobs that have a workspace on the same agent. The issue is fixed in Jenkins 2.588.0 and LTS 2.580.2.