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 (top 0.4% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 14 internet-exposed hosts are running an affected version right now
  • 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: 14

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.

Live · internet exposure

14 internet-exposed hosts are running an affected version of CVE-2016-0792 right now.

across 7 countries (United States, China, Bangladesh, Netherlands, United Kingdom)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
8.8
EG Score
9.0(high)
EG Risk
78(Track)
EG Risk 78/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
83%
EPSS %ILE
100%
KEV
Not listed

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🟡 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 / 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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 22× 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-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
Show 29 more
  1. 2026-06-23 16:30 UTCOSV refresh
  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-16 17:50 UTCEPSS rescore
  7. 2026-06-16 17:50 UTCEPSS rescore
  8. 2026-06-15 17:45 UTCEPSS rescore
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-10 22:15 UTCEPSS rescore
  12. 2026-06-10 13:18 UTCEPSS rescore
  13. 2026-06-08 14:14 UTCEPSS rescore
  14. 2026-06-06 21:59 UTCOSV refresh
  15. 2026-06-05 22:44 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:08 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-05-31 00:14 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-22 20:59 UTCEG score recompute
  23. 2026-05-22 20:59 UTCVendor advisory
  24. 2026-05-22 17:43 UTCOSV refresh
  25. 2026-05-21 22:40 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-43375✓ verified
    First seen Dec 19, 2017

    Jenkins - XStream Groovy classpath Deserialization (Metasploit)

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

    Jenkins < 1.650 - Java Deserialization

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

    Exploit for Jenkins serialization vulnerability - CVE-2016-0792

    Open source ↗
  • Metasploitexploit/multi/http/jenkins_xstream_deserialize✓ verified
    First seen Feb 24, 2016

    Jenkins XStream Groovy classpath Deserialization Vulnerability

    Open source ↗

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 in the National Vulnerability Database 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. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all 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.
How do I remediate CVE-2016-0792?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0792, 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-0792

Explore →

Is Your Infrastructure Affected by CVE-2016-0792?

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