Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2016-0792: Jenkins Remote API XML Deserialization RCE

Published Apr 7, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3
EPSS83.3%100th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
JenkinsRed Hat
IdentifiersCVE-2016-0792CWE-502

CVE-2016-0792 is an unsafe deserialization vulnerability in Jenkins before 1.650 and Jenkins LTS before 1.642.2. Multiple unspecified remote API endpoints process serialized XML using XStream in a manner involving groovy.util.Expando. An authenticated user can supply crafted serialized XML that causes arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote authenticated attacker to execute arbitrary code in the security context of the Jenkins process. This can compromise Jenkins configuration, credentials and build infrastructure, manipulate jobs and artifacts, and provide a foothold for further activity in connected environments.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to Jenkins API endpoints that accept XML input to trusted administrators only, minimize the number of authenticated users, and place Jenkins behind network access controls. Monitor for suspicious XML-based API requests and unexpected code execution behavior on the Jenkins controller. These are temporary risk-reduction measures and do not replace upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade Jenkins to version 1.650 or later, or Jenkins LTS to version 1.642.2 or later. For affected Red Hat OpenShift Enterprise deployments, apply the applicable vendor security update containing the corrected Jenkins package or container image.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
jenkins_xstream_deserialize.rbThis repository contains a single Metasploit module (jenkins_xstream_deserialize.rb) that exploits CVE-2016-0792, a remote code execution vulnerability in Jenkins (pre-1.650 and LTS pre-1.642.2) due to unsafe XStream deserialization with Groovy in the classpath. The exploit is weaponized, supporting multiple platforms (Windows, Linux, Unix, Python) and payload types (command execution, staged payloads, droppers). It does not require authentication and targets the Jenkins HTTP interface, specifically the '/createItem' endpoint. The module checks for vulnerable Jenkins versions by inspecting the 'X-Jenkins' HTTP header. The exploit works by sending a crafted XML payload that triggers code execution via Groovy's Expando and Java's ProcessBuilder. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.Disclosed Feb 24, 2016 · Framework: metasploit · ruby · networkWeaponizedjenkins-cve-2016-0792This repository contains a Python-based exploit for Jenkins CVE-2016-0792, a remote code execution vulnerability in Jenkins versions prior to 1.650. The main exploit logic resides in 'exploit.py', which checks if the target Jenkins server is online, verifies its version via the 'X-Jenkins' HTTP header, and if vulnerable, sends a crafted XML payload to the '/createItem' endpoint to trigger command execution. The payload is generated by 'prepare_payload.py', which constructs an XML object that leverages Groovy's Expando and Java's ProcessBuilder to execute arbitrary commands. The exploit requires Python 3.6+ and the 'requests' library. The README provides usage instructions and references to further documentation. No hardcoded IPs or credentials are present; the exploit is generic and requires the attacker to specify the target URL and command to execute. The attack vector is network-based, targeting Jenkins servers accessible over HTTP.jpiechowka · Disclosed Jul 30, 2017 · python · networkOperationalCVE-2016-0792This repository contains a Python exploit script (CVE-2016-0792.py) targeting Jenkins servers vulnerable to CVE-2016-0792, a remote code execution vulnerability. The exploit works by programmatically creating a new Jenkins job with a malicious shell command payload, which runs an exfiltration binary in the background, monitors its process, and attempts to contact an exfiltration server at http://exfiltration:8080. The script then triggers the job and monitors its output via Jenkins' API. The exploit assumes the Jenkins server is accessible at http://web:8080 and that the exfiltration binary is present at /usr/local/bin/exfiltrate. The repository also includes a minimal README. The main attack vector is network-based, exploiting Jenkins' job creation and build features to achieve remote code execution. The script is operational and demonstrates a real-world attack scenario, though it requires a specific environment (vulnerable Jenkins, exfiltration binary, and exfiltration server) to function fully.bugdotexe · Disclosed Jul 15, 2025 · python · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
JenkinsJenkinsapplication
Red HatOpenshiftapplication
FAQ

Frequently asked questions

Is CVE-2016-0792 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2016-0792?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2016-0792, the earliest disclosed Feb 24, 2016.
Is there a patch for CVE-2016-0792?
Upgrade Jenkins to version 1.650 or later, or Jenkins LTS to version 1.642.2 or later. For affected Red Hat OpenShift Enterprise deployments, apply the applicable vendor security update containing the corrected Jenkins package or container image.
What products are affected by CVE-2016-0792?
Jenkins and Red Hat Openshift.
How severe is CVE-2016-0792?
CVE-2016-0792 has a CVSS v3 score of 8.8 (High) and an EPSS score of 83.3% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.