Loading vulnerability…
Jenkins 2.56 and earlier, and Jenkins LTS 2.46.1 and earlier, contain an unauthenticated remote code execution vulnerability in the CLI subsystem. The flaw arises because the Jenkins CLI accepted a serialized Java SignedObject that was deserialized via a new ObjectInputStream, allowing attackers to bypass the product’s existing blacklist-based deserialization protections. By sending a crafted serialized object to the Jenkins CLI endpoint, a remote attacker could trigger deserialization of untrusted data and achieve arbitrary code execution on the Jenkins server without authentication.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
SignedObject to the deserialization blacklist, backporting the newer HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based Java-serialization CLI protocol, which is disabled by default in the fixed line. Fixed releases include Jenkins 2.57 and Jenkins LTS 2.46.2 or later.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository is a proof-of-concept exploit for Jenkins CVE-2017-1000353, a Java deserialization vulnerability in the Jenkins CLI endpoint. The exploit consists of a Python script (exploit.py) that sends a malicious serialized Java object (generated by Payload.java) to the Jenkins /cli endpoint. The Java payload is crafted to execute arbitrary system commands on the Jenkins server when deserialized. The README provides detailed usage instructions, including payload generation and exploitation steps. The exploit requires a vulnerable Jenkins instance and a compatible Java version (tested with openjdk:8u292). The main attack vector is network-based, targeting the Jenkins HTTP interface. The exploit demonstrates successful code execution by creating a file at /tmp/success on the target system. The repository includes Python and Java code, as well as build configuration files for the Java payload.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote code execution vulnerability in Jenkins that allows unauthenticated attackers to bypass deserialization safeguards via crafted Java SignedObject through the CLI.
A deserialization of untrusted data vulnerability in Jenkins allows unauthenticated remote code execution, bypassing denylist-based protections.
Jenkins deserialization vulnerability enabling unauthenticated remote code execution, bypassing existing protections.
A Jenkins CLI Java deserialization remote code execution vulnerability allowing crafted serialized objects to execute arbitrary code without authentication.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.