CVE-2017-1000353
CVE-2017-1000353 is a security flaw in Jenkins. Attackers can run their own code on Jenkins from anywhere, without logging in. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 2 Oct 2025.[1]
Jenkins is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Jenkins has published a fix or advice.
Description
CISA calls it a remote code execution in Jenkins Jenkins. In its words: “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.”[1]
The CVE record adds: “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.”[2]
The underlying weakness is deserialization of untrusted data (CWE-502), in MITRE’s list of common software weaknesses.
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; Jenkins’s advisory has them[3]. CISA names the product as Jenkins Jenkins.
Most families won’t have Jenkins; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 2 Oct 2025, 2,803 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 23 Oct 2025 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at over 99%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
Jenkins has published a fix or advice.[3] CISA’s 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.”[1]
- Check whether you use it.Jenkins is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 23 Oct 2025 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at over 99%.[4] |
See also
Other Jenkins flaws
- CVE-2024-23897, Jenkins Command Line Interface (CLI): command line interface (CLI) path traversal ·
- CVE-2015-5317, Jenkins User Interface (UI): user interface (UI) information disclosure ·
- CVE-2019-1003029, Jenkins Script Security Plugin: sandbox bypass ·
- CVE-2019-1003030, Jenkins Matrix Project Plugin: remote code execution ·
- CVE-2018-1000861, Jenkins Stapler Web Framework: stapler web framework deserialization of untrusted data ·
Other deserialization of untrusted data flaws
- CVE-2021-23758, Ajax.NET Professional: deserialization of untrusted data ·
- CVE-2026-63077, JetBrains TeamCity: deserialization of untrusted data ·
- CVE-2026-50522, Microsoft SharePoint: deserialization of untrusted data ·
- CVE-2026-58644, Microsoft SharePoint: deserialization of untrusted data ·
- CVE-2026-45659, Microsoft SharePoint Server: deserialization of untrusted data ·
Added the same day
- CVE-2025-4008, Smartbedded Meteobridge: command injection ·
- CVE-2025-21043, Samsung Mobile Devices: out-of-bounds write ·
- CVE-2015-7755, Juniper ScreenOS: improper authentication ·
- CVE-2014-6278, GNU Bash: bash OS command injection ·
Every Jenkins flaw on CISA’s list · Everything added in October 2025
References
- ^ Cybersecurity and Infrastructure Security Agency. “Jenkins Remote Code Execution Vulnerability”. Known Exploited Vulnerabilities Catalog, added 2 Oct 2025.
- ^ National Institute of Standards and Technology. “CVE-2017-1000353 Detail”. National Vulnerability Database, published 29 Jan 2018.
- ^ Jenkins. Advisories and fixes: jenkins.io, jenkins.io, oracle.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.997, percentile 100.0, 31 Oct 2026.
- CVE Program. “CVE-2017-1000353”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.