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 version 1.650 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

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 90.6%, 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 April 16, 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

CVE-2016-0792

HIGH

Jenkins allows Deserialization of Untrusted Data via an XML File

Also known asGHSA-45rg-g72w-r393

Published

Apr 7, 2016

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

10 known

EPSS Exploitation Probability

via FIRST.org ↗

90.6%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	1.642.2

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-0792 in your stack?

O3 detects CVE-2016-0792 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works