Exploited vulnerability · CISA KEV
Yes. CVE-2017-1000353, Jenkins Remote Code Execution Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 2 Oct 2025, 2803 days after it was published. It affects Jenkins. If you run it, CISA's required action is: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
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.
| Vendor | Jenkins (6 exploited CVEs in KEV) |
| Product | Jenkins |
| Vulnerability | Jenkins Remote Code Execution Vulnerability |
| Weakness | not specified |
| Published | 29 Jan 2018 |
| Added to KEV | 2 Oct 2025 |
| Reported by (CNA) | mitre |
Yes. CISA added CVE-2017-1000353 to the Known Exploited Vulnerabilities catalog on 2 Oct 2025, which means there is reliable evidence of exploitation in the wild.
CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Check Jenkins's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Jenkins and watch it for signs of compromise.
Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in October 2025 · Jenkins scorecard · act-now radar.
We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.
Get in touch →