CVE-2016-0788

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 37.4%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 12%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
95.6%
KEV
Not listed

Published

April 7, 2016

Last Modified

May 6, 2026

Advisory Details (3)

Auto-updated May 7, 2026
Patch available. Sources: redhat.
generic

Jenkins Security Advisory 2016-02-24

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24
redhat Patch Available
https://access.redhat.com/errata/RHSA-2016:0711
generic
http://rhn.redhat.com/errata/RHSA-2016-1773.html

Vendor Advisories for CVE-2016-0788(2)

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-routing-daemon-0:0.26.6.1-1.el6op2016-08-24redhat
redhatjenkins-plugin-openshift-pipeline-0:1.0.9-1.el72016-05-03redhat

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.396 ... 1.642.1 (300 versions)1.642.2—

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2016-0788?
CVE-2016-0788 is a critical vulnerability published on April 7, 2016. The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener.
When was CVE-2016-0788 disclosed?
CVE-2016-0788 was first published in the National Vulnerability Database on April 7, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-0788 actively exploited?
CVE-2016-0788 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-0788?
CVE-2016-0788 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-0788?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0788, 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-2016-0788

Explore →

Is Your Infrastructure Affected by CVE-2016-0788?

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

Start Free Scan →Browse All CVEs