CVE-2015-5317

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-05-12), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 13 internet-exposed hosts are running an affected version right now
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 22%CVSS: 7.5Exploit: cisa kev · ssvc active · epss top5pctExposed: 13

A fix is available — apply it.

The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request.

Live · internet exposure

13 internet-exposed hosts are running an affected version of CVE-2015-5317 right now.

across 6 countries (United States, China, Bangladesh, Indonesia, Netherlands)top: jenkins
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
96(Attend)
EG Risk 96/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
22%
EPSS %ILE
97%
KEV
⚠ Exploited

Published

November 25, 2015

Last Modified

April 22, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: redhat, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2015-5317
generic

Jenkins Security Advisory 2015-11-11

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:0070
generic
http://rhn.redhat.com/errata/RHSA-2016-0489.html

Vendor Advisories for CVE-2015-5317(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-openshift-origin-node-0:1.38.5.3-1.el6op2016-03-22redhat
redhatorigin-kibana-0:0.5.0-1.el7aos2016-01-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jenkins-ci.main:jenkins-core1.626 ... 1.637 (12 versions)1.638—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 42× in last 7d / 218× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 460 total refreshes for this CVE.

  1. 2026-07-27 07:15 UTCVendor advisory
  2. 2026-07-27 03:09 UTCVendor advisory
  3. 2026-07-26 23:03 UTCVendor advisory
  4. 2026-07-26 18:58 UTCVendor advisory
  5. 2026-07-26 14:53 UTCEG score recompute
  6. 2026-07-26 14:53 UTCVendor advisory
  7. 2026-07-26 14:50 UTCEPSS rescore
  8. 2026-07-26 10:48 UTCEG score recompute
  9. 2026-07-26 10:48 UTCVendor advisory
  10. 2026-07-26 06:43 UTCVendor advisory
  11. 2026-07-26 02:37 UTCEG score recompute
  12. 2026-07-26 02:37 UTCVendor advisory
  13. 2026-07-25 14:13 UTCEPSS rescore
  14. 2026-07-24 14:13 UTCEPSS rescore
  15. 2026-07-23 14:14 UTCEPSS rescore
  16. 2026-07-23 01:18 UTCEG score recompute
  17. 2026-07-23 00:20 UTCEG score recompute
  18. 2026-07-22 21:50 UTCEG score recompute
  19. 2026-07-22 21:50 UTCVendor advisory
  20. 2026-07-22 19:40 UTCCISA KEV update
  21. 2026-07-22 17:40 UTCEG score recompute
  22. 2026-07-22 17:40 UTCVendor advisory
  23. 2026-07-22 14:04 UTCEPSS rescore
  24. 2026-07-22 13:33 UTCVendor advisory
  25. 2026-07-22 09:29 UTCVendor advisory
Show 75 more
  1. 2026-07-22 05:23 UTCVendor advisory
  2. 2026-07-22 01:10 UTCVendor advisory
  3. 2026-07-21 19:50 UTCVendor advisory
  4. 2026-07-21 15:34 UTCEG score recompute
  5. 2026-07-21 15:34 UTCVendor advisory
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-21 14:37 UTCCISA KEV update
  9. 2026-07-21 11:28 UTCVendor advisory
  10. 2026-07-21 07:24 UTCVendor advisory
  11. 2026-07-21 03:19 UTCVendor advisory
  12. 2026-07-20 23:14 UTCVendor advisory
  13. 2026-07-20 19:09 UTCEG score recompute
  14. 2026-07-20 19:09 UTCVendor advisory
  15. 2026-07-20 17:03 UTCEPSS rescore
  16. 2026-07-20 15:05 UTCVendor advisory
  17. 2026-07-20 10:58 UTCVendor advisory
  18. 2026-07-20 06:53 UTCVendor advisory
  19. 2026-07-20 02:45 UTCVendor advisory
  20. 2026-07-19 22:40 UTCVendor advisory
  21. 2026-07-19 18:35 UTCVendor advisory
  22. 2026-07-19 14:30 UTCEG score recompute
  23. 2026-07-19 14:30 UTCVendor advisory
  24. 2026-07-19 14:27 UTCEPSS rescore
  25. 2026-07-19 14:27 UTCEPSS rescore
  26. 2026-07-19 10:26 UTCVendor advisory
  27. 2026-07-19 06:21 UTCEG score recompute
  28. 2026-07-19 06:21 UTCVendor advisory
  29. 2026-07-19 02:26 UTCEPSS rescore
  30. 2026-07-19 02:26 UTCEPSS rescore
  31. 2026-07-19 02:16 UTCVendor advisory
  32. 2026-07-18 22:11 UTCVendor advisory
  33. 2026-07-18 18:07 UTCVendor advisory
  34. 2026-07-18 14:01 UTCEG score recompute
  35. 2026-07-18 14:01 UTCVendor advisory
  36. 2026-07-18 10:00 UTCEPSS rescore
  37. 2026-07-18 09:56 UTCVendor advisory
  38. 2026-07-18 05:51 UTCVendor advisory
  39. 2026-07-18 01:46 UTCVendor advisory
  40. 2026-07-17 21:41 UTCVendor advisory
  41. 2026-07-17 17:36 UTCVendor advisory
  42. 2026-07-17 13:31 UTCVendor advisory
  43. 2026-07-17 09:26 UTCEG score recompute
  44. 2026-07-17 09:26 UTCVendor advisory
  45. 2026-07-17 05:22 UTCVendor advisory
  46. 2026-07-17 01:17 UTCVendor advisory
  47. 2026-07-16 21:11 UTCVendor advisory
  48. 2026-07-16 17:06 UTCVendor advisory
  49. 2026-07-16 17:04 UTCCISA KEV update
  50. 2026-07-16 16:59 UTCEPSS rescore
  51. 2026-07-16 13:00 UTCVendor advisory
  52. 2026-07-16 08:55 UTCVendor advisory
  53. 2026-07-16 04:50 UTCVendor advisory
  54. 2026-07-16 00:45 UTCVendor advisory
  55. 2026-07-15 20:40 UTCVendor advisory
  56. 2026-07-15 16:54 UTCEPSS rescore
  57. 2026-07-15 16:54 UTCEPSS rescore
  58. 2026-07-15 16:49 UTCCISA KEV update
  59. 2026-07-15 16:34 UTCVendor advisory
  60. 2026-07-15 15:04 UTCCISA KEV update
  61. 2026-07-15 12:30 UTCVendor advisory
  62. 2026-07-15 08:24 UTCVendor advisory
  63. 2026-07-15 04:18 UTCVendor advisory
  64. 2026-07-15 01:56 UTCEPSS rescore
  65. 2026-07-15 00:12 UTCVendor advisory
  66. 2026-07-14 20:07 UTCVendor advisory
  67. 2026-07-14 18:05 UTCCISA KEV update
  68. 2026-07-14 16:00 UTCVendor advisory
  69. 2026-07-14 11:56 UTCVendor advisory
  70. 2026-07-14 07:52 UTCVendor advisory
  71. 2026-07-14 03:45 UTCVendor advisory
  72. 2026-07-13 23:40 UTCVendor advisory
  73. 2026-07-13 22:26 UTCEPSS rescore
  74. 2026-07-13 22:26 UTCEPSS rescore
  75. 2026-07-13 19:35 UTCVendor advisory

Related CVEs(same vendor)

Frequently asked(6)

What is CVE-2015-5317?
CVE-2015-5317 is a critical vulnerability published on November 25, 2015. The Fingerprints pages in Jenkins before 1.638 and LTS before 1.625.2 might allow remote attackers to obtain sensitive job and build name information via a direct request.
When was CVE-2015-5317 disclosed?
CVE-2015-5317 was first published in the National Vulnerability Database on November 25, 2015, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-5317 actively exploited?
Yes. CISA added CVE-2015-5317 to the Known Exploited Vulnerabilities catalog on May 12, 2023, affecting Jenkins Jenkins User Interface (UI). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2015-5317?
CVE-2015-5317 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2015-5317?
CVE-2015-5317 affects Jenkins Jenkins User Interface (UI). The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2015-5317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-5317, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-5317

Explore →

Is Your Infrastructure Affected by CVE-2015-5317?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs