Jenkins 2.587 and earlier, LTS 2.580.1 and earlier does not restrict item types in collections after deserialization
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
Until a fix is available, restrict access to the POST config.xml API endpoint to trusted users only to reduce the risk of exploitation.
Description
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where item types in collections are not restricted after deserialization. This flaw allows attackers with access to POST config.xml API endpoints to submit crafted configuration files that can lead to stored cross-site scripting (XSS) vulnerabilities.