Jenkins Remote Code Execution Vulnerability
n/a — n/a
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.
9.8
99.7%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- Jan 29, 2018
- Modified
- Oct 21, 2025
- Added to KEV
- Oct 2, 2025
- Federal patch due
- Oct 23, 2025
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.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2017-1000353, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2017-1000353 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2017-1000353?
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.
How severe is CVE-2017-1000353?
CVE-2017-1000353 has a CVSS base score of 9.8 out of 10 (CVSS 3.1).
Is CVE-2017-1000353 actively exploited in the wild?
Yes. CVE-2017-1000353 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Oct 2, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2017-1000353?
99.7% - meaning FIRST.org's EPSS model estimates a 99.7% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
What type of vulnerability is CVE-2017-1000353?
CVE-2017-1000353 is classified under CWE-502 (CWE-502 Deserialization of Untrusted Data).
Cross-checked against
Impactr finds and proves whether CVE-2017-1000353 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist