CVE-2017-1000353: Jenkins Remote Code Execution Vulnerability

Should you act?

Exploited: patch now if you run it

CISA has confirmed exploitation in the wild. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Yes, if you run Jenkins Jenkins. CISA added this CVE to its Known Exploited Vulnerabilities catalog on 2025-10-02, which means there is reliable evidence of exploitation in the wild. US federal agencies must remediate by 2025-10-23; treat that as the outer limit, not the target.
• EPSS 99.7%, percentile 100.0: FIRST’s model estimates a 99.7% chance of exploitation activity in the next 30 days, higher than 100.0% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.

What it is

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’s summary

Jenkins contains a remote code execution vulnerability. This vulnerability that could allowed attackers to transfer a serialized Java SignedObject object to the remoting-based Jenkins CLI, that would be deserialized using a new ObjectInputStream, bypassing the existing blocklist-based protection mechanism.

Weakness type: CWE-502.

Product: Jenkins Jenkins · Assigned by: mitre · Published: 2018-01-29

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: added 2025-10-02; federal due date 2025-10-23. Known ransomware use: Unknown.
• 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 SSVC assessment: exploitation active, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 99.68% probability of exploitation activity in the next 30 days; percentile 100.0.

Timeline

• 2018-01-29 — CVE record published by mitre
• 2025-10-02 — Added to CISA’s Known Exploited Vulnerabilities catalog
• 2025-10-21 — CVE record last updated
• 2025-10-23 — CISA remediation deadline for US federal agencies

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. Listed in CISA KEV notes (jenkins.io) jenkins.io

Vulnerability records

1. CVE.org record CVE-2017-1000353 cve.org
2. NVD entry CVE-2017-1000353 nvd.nist.gov

Government

1. CISA Known Exploited Vulnerabilities catalog entry cisa.gov

Other references from the CVE record and advisory

1. 41965 exploit-db.com
2. 98056 securityfocus.com
3. oracle.com oracle.com
4. jenkins.io jenkins.io
5. packetstormsecurity.com packetstormsecurity.com

All exploited Jenkins vulnerabilities · Today’s Security Digest