CVE-2016-0792

CRITICALNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 83% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 44 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 83%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 83%CVSS: 8.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: 44

A fix is available — apply it.

Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and groovy.util.Expando.

Internet exposure · derived from Shodan data

44 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2016-0792, in our KEV-Exposure radar’s Shodan-derived sample.

across 14 countries (United States, Germany, China, Japan, France)top: jenkins
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
78
EG Risk 78/100CISA SSVC

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%
Exploitation83% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
83%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 7, 2016

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated May 22, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic

Serialization Must Die: Act 2: XStream (Jenkins CVE-2016-0792)

https://www.contrastsecurity.com/security-influencers/serialization-must-die-act-2-xstream
generic

Jenkins Security Advisory 2016-02-24

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2016:0711
generic
http://rhn.redhat.com/errata/RHSA-2016-1773.html
generic🟡 PoC Available

Jenkins - XStream Groovy classpath Deserialization (Metasploit) - Multiple remote Exploit

https://www.exploit-db.com/exploits/43375/
generic🟡 PoC Available

Jenkins < 1.650 - Java Deserialization - Java remote Exploit

https://www.exploit-db.com/exploits/42394/

Vendor Advisories for CVE-2016-0792(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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
org.jenkins-ci.main:jenkins-core1.396 ... 1.642.1 (300 versions)
  • 1.643 up to 1.650: fixed in 1.650
  • every version up to 1.642.2: fixed in 1.642.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 8× 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-10-10 19:54 UTCEPSS rescore
  2. 2026-10-08 19:55 UTCOSV refresh
  3. 2026-10-07 23:40 UTCEPSS rescore
  4. 2026-10-05 17:38 UTCEPSS rescore
  5. 2026-09-30 09:09 UTCEG score recompute
  6. 2026-09-19 02:00 UTCOSV refresh
  7. 2026-09-18 19:22 UTCEPSS rescore
  8. 2026-09-17 19:21 UTCEPSS rescore
  9. 2026-09-10 09:26 UTCEPSS rescore
  10. 2026-09-06 13:42 UTCEPSS rescore
  11. 2026-09-04 13:55 UTCEPSS rescore
  12. 2026-09-02 14:07 UTCEPSS rescore
  13. 2026-08-31 05:49 UTCOSV refresh
  14. 2026-08-27 14:20 UTCEPSS rescore
  15. 2026-08-26 14:41 UTCEPSS rescore
  16. 2026-08-25 13:44 UTCEPSS rescore
  17. 2026-08-21 23:44 UTCEPSS rescore
  18. 2026-08-19 16:59 UTCEPSS rescore
  19. 2026-08-15 01:25 UTCEPSS rescore
  20. 2026-08-14 12:54 UTCOSV refresh
  21. 2026-08-12 13:46 UTCEPSS rescore
  22. 2026-08-05 19:12 UTCEPSS rescore
  23. 2026-07-30 01:54 UTCOSV refresh
  24. 2026-07-30 01:26 UTCEPSS rescore
  25. 2026-07-30 01:26 UTCEPSS rescore
Show 54 more
  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-25 14:13 UTCEPSS rescore
  3. 2026-07-24 14:13 UTCEPSS rescore
  4. 2026-07-23 01:21 UTCEG score recompute
  5. 2026-07-23 00:22 UTCEG score recompute▲ 0.20
  6. 2026-07-22 22:00 UTCEG score recompute▼ 0.20
  7. 2026-07-22 14:04 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-20 17:03 UTCEPSS rescore
  11. 2026-07-19 14:27 UTCEPSS rescore
  12. 2026-07-19 14:27 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-15 16:54 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-12 11:07 UTCOSV refresh
  17. 2026-07-11 08:23 UTCEPSS rescore
  18. 2026-07-08 15:10 UTCEPSS rescore
  19. 2026-07-04 06:28 UTCEPSS rescore
  20. 2026-07-01 15:02 UTCEPSS rescore
  21. 2026-06-30 23:19 UTCEPSS rescore
  22. 2026-06-30 23:19 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
  26. 2026-06-23 16:30 UTCOSV refresh
  27. 2026-06-21 14:54 UTCEPSS rescore
  28. 2026-06-21 14:54 UTCEPSS rescore
  29. 2026-06-21 01:57 UTCEPSS rescore
  30. 2026-06-21 01:57 UTCEPSS rescore
  31. 2026-06-16 17:50 UTCEPSS rescore
  32. 2026-06-16 17:50 UTCEPSS rescore
  33. 2026-06-15 17:45 UTCEPSS rescore
  34. 2026-06-14 23:14 UTCEPSS rescore
  35. 2026-06-13 22:57 UTCEPSS rescore
  36. 2026-06-10 22:15 UTCEPSS rescore
  37. 2026-06-10 13:18 UTCEPSS rescore
  38. 2026-06-08 14:14 UTCEPSS rescore
  39. 2026-06-06 21:59 UTCOSV refresh
  40. 2026-06-05 22:44 UTCEPSS rescore
  41. 2026-06-05 06:08 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-02 20:10 UTCEPSS rescore
  44. 2026-05-31 00:14 UTCEPSS rescore
  45. 2026-05-26 07:16 UTCEPSS rescore
  46. 2026-05-26 07:16 UTCEPSS rescore
  47. 2026-05-22 20:59 UTCEG score recompute
  48. 2026-05-22 20:59 UTCVendor advisory
  49. 2026-05-22 17:43 UTCOSV refresh
  50. 2026-05-21 22:40 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 22:37 UTCEPSS rescore
  53. 2026-05-18 21:30 UTCEPSS rescore
  54. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-43375✓ verified
    Published Dec 19, 2017

    Jenkins - XStream Groovy classpath Deserialization (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/jenkins_xstream_deserialize✓ verified
    Published Dec 18, 2017

    Jenkins XStream Groovy classpath Deserialization Vulnerability

    Open source ↗
  • Exploit-DBEDB-42394✓ verified
    Published Jul 30, 2017

    Jenkins < 1.650 - Java Deserialization

    Open source ↗
  • GitHub PoCjpiechowka/jenkins-cve-2016-0792
    Published Jul 30, 2017

    Exploit for Jenkins serialization vulnerability - CVE-2016-0792

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-0792?
CVE-2016-0792 is a critical vulnerability published on April 7, 2016. Multiple unspecified API endpoints in Jenkins before 1.650 and LTS before 1.642.2 allow remote authenticated users to execute arbitrary code via serialized data in an XML file, related to XStream and groovy.util.Expando.
When was CVE-2016-0792 disclosed?
CVE-2016-0792 was first published on April 7, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-0792 actively exploited?
CVE-2016-0792 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-0792?
CVE-2016-0792 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2016-0792?
A fix for CVE-2016-0792 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-0792 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-0792

Explore →

Is Your Infrastructure Affected by CVE-2016-0792?

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

Book a Demo →Browse All CVEs