How to check if you are exposed to CVE-2015-5317
- Find every Jenkins User Interface (UI) system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2015-5317.
US federal agencies had to fix this by 2023-06-02. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Timeline
- · Added to CISA's Known Exploited Vulnerabilities catalog
- · Fix-by date for US federal agencies, passed 1,248 days ago
Vendor advisories and fixes
Weakness type
More exploited Jenkins vulnerabilities
CISA lists 6 exploited Jenkins vulnerabilities. The closest matches:
- CVE-2017-1000353Jenkins Remote Code Execution VulnerabilityAdded 2025-10-02
- CVE-2024-23897Jenkins Command Line Interface (CLI) Path Traversal VulnerabilityAdded 2024-08-19
- CVE-2019-1003029Jenkins Script Security Plugin Sandbox Bypass VulnerabilityAdded 2022-04-25
- CVE-2019-1003030Jenkins Matrix Project Plugin Remote Code Execution VulnerabilityAdded 2022-03-25
- CVE-2018-1000861Jenkins Stapler Web Framework Deserialization of Untrusted Data VulnerabilityAdded 2022-02-10
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.
