How severe is CVE-2016-0792?

CVE-2016-0792 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-0792?

CVE-2016-0792 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-0792?

Update org.jenkins-ci.main:jenkins-core to 1.650 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0792 is resolved across your whole dependency graph.

How do I detect CVE-2016-0792 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2016-0792 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2016-0792 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2016-0792, including 2 documented proof-of-concept exploits on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-0792?

CVE-2016-0792 has an EPSS (Exploit Prediction Scoring System) score of 83.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2016-0792?

CVE-2016-0792 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2016-0792 published, and has it been updated?

CVE-2016-0792 was published on April 7, 2016 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2016-0792 — jenkins-core

HIGHFix: jenkinsci/jenkins@7f202f0

CVE-2016-0792 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in org.jenkins-ci.main:jenkins-core. 10 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Jenkins allows Deserialization of Untrusted Data via an XML File

Also known asGHSA-45rg-g72w-r393

Published

Apr 7, 2016

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

10 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

83.3%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 1.643&&< 1.650	1.650`org.jenkins-ci.main:jenkins-core:1.650`
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	1.642.2`org.jenkins-ci.main:jenkins-core:1.642.2`

Affected Products

2 products · 3 configurations

Application

jenkinsjenkins

≤ 1.642.1

range

Application

openshiftredhat

1 version

3.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42394remotejava✓ Verified

Jenkins < 1.650 - Java Deserialization

by Janusz Piechówka · Jul 30, 2017

Exploit-DB Source

EDB-43375remotemultiple✓ Verified

Jenkins - XStream Groovy classpath Deserialization (Metasploit)

by Metasploit · Dec 19, 2017

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 1.650 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0792 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift Enterprise 2.2	`activemq-0:5.9.0-6.redhat.611463.el6op`	RHSA-2016:1773
Red Hat OpenShift Enterprise 3.1	`jenkins-0:1.642.2-1.el7`	RHSA-2016:0711

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-0792 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-20Improper Input Validation

Weaponization

No Nuclei template or Metasploit module yet. 10 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

jenkins

6.4/10

Code-Review6/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Apr 7, 2016

First exploit

Jul 30, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2016-0792

GHSA-45rg-g72w-r393

References

Advisoryrhn.redhat.com · RHSA 2016 1773 Advisoryaccess.redhat.com · RHSA 2016:0711 Advisorynvd.nist.gov · CVE 2016 0792 Fixwiki.jenkins-ci.org · Jenkins+Security+Advisory+2016 02 24 Webexploit-db.com Webexploit-db.com Webgithub.com · 7f202f0317e60cd3160f61467b8558f864f83f41 Webexploit-db.com Webexploit-db.com Packagegithub.com · jenkins Evidencecontrastsecurity.com · serialization must die act 2 xstream

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs affecting jenkins-core are rated as high or higher (top: high).

CVE-2026-53436CVE-2026-53437CVE-2026-53440CVE-2026-53441CVE-2026-53439CVE-2026-53435CVE-2026-53442CVE-2026-53438

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2016-0792 — jenkins-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2016-0792 in your dependencies?