Skip to content
Server Security Center
KEVcritical9.8

CVE-2017-1000353: Jenkins Remote Code Execution

Jenkins · listed in the CISA catalog of actively exploited vulnerabilities since 2025-10-02.

CVSS v3.1 (CISA ADP)
9.8
critical
EPSS (exploit probability, 30 days)
99.6%
among the highest 0.1% of all CVEs
Added to CISA KEV
2025-10-02
US federal due date 2025-10-23
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2017-1000353 explained

CVE-2017-1000353 is an unauthenticated remote code execution vulnerability in the Jenkins automation server. It comes from unsafe deserialization of Java objects sent to the Jenkins CLI, which bypasses the existing blacklist-based protection. CISA lists it as known to be exploited, so unpatched Jenkins servers that are reachable on the network face serious risk.

Impact

A remote attacker without credentials or user interaction can send a crafted serialized Java object to the Jenkins CLI and execute code on the server. Confidentiality, integrity and availability impact are all high. CISA rates the flaw as automatable, meaning it can be exploited at scale, with total technical impact: full control of the Jenkins server. CISA lists it as known to be exploited. Whether ransomware actors use it is unknown.

Who is affected

The description states that Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier, are vulnerable. The CVE record itself lists no structured affected versions. The record names no fixed version. Check the Jenkins security advisory to confirm which release fixes the issue for your weekly or LTS line.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: jenkins.io/security/advisory/2017-04-26
  • CISA's deadline for US federal agencies: 2025-10-23 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all Jenkins instances and check whether they run 2.56 or earlier, or 2.46.1 LTS or earlier.
  2. Upgrade to a fixed Jenkins release as identified in the vendor's security advisory.
  3. Make sure the remoting-based (Java serialization) CLI protocol is disabled, as described in the vendor's fix.
  4. Restrict network access to Jenkins and its CLI. Do not expose these services directly to the internet.
  5. Check exposed Jenkins servers for signs of compromise, such as unexpected jobs, accounts or processes.

The CVE record names no fixed version. Follow the Jenkins security advisory to find the fixed release and apply it. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use if mitigations are unavailable. Until you upgrade, block untrusted network access to Jenkins and its CLI.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-502 Deserialization of Untrusted Data

Questions about CVE-2017-1000353

Does an attacker need a Jenkins account to exploit this?
No. The vulnerability allows unauthenticated remote code execution over the network, with no user interaction required.
Is this vulnerability being exploited?
Yes. CISA added CVE-2017-1000353 to its Known Exploited Vulnerabilities catalog on 2025-10-02, with a US federal due date of 2025-10-23. Ransomware use is listed as unknown.
What did the vendor change to fix it?
According to the description, the vendor added the abused object type to the deserialization blacklist. It also deprecated the remoting-based CLI protocol and disabled it by default, in favour of a new HTTP CLI protocol.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.