Live › vulnerability › CVE-2017-1000353
Go to dashboardJenkins has a remote code execution flaw in its remoting-based CLI, where a crafted serialized Java SignedObject bypasses the blocklist that normally blocks dangerous deserialization. An attacker who can reach the CLI port can run code on the Jenkins controller, and CISA lists it as actively exploited.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Jenkins Jenkins | vendor | – | – |
| jenkins | vendor | <= 2.56 | – |
| jenkins | vendor | <= 2.46.1 | – |
| oracle communications cloud native core automated test suite | vendor | = 1.9.0 | – |
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution. An unauthenticated remote code execution vulnerability allowed attackers to transfer a serialized Java SignedObject object to the Jenkins CLI, that would be deserialized using a new ObjectInputStream, bypassing the existing blacklist-based protection mechanism. We're fixing this issue by adding SignedObject to the blacklist. We're also backporting the new HTTP CLI protocol from Jenkins 2.54 to LTS 2.46.2, and deprecating the remoting-based (i.e. Java serialization) CLI protocol, disabling it by default.
This page as .md · .json · in your agent: get_signal("CVE-2017-1000353")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.