Jenkins · Jenkins · published 2018-01-29

CVE-2017-1000353Jenkins Remote Code Execution Vulnerability

Patch today Known exploited server software, exploitation is automatable, total technical impact.

CVE-2017-1000353 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-10-02. EPSS estimates a 99.7% chance of exploitation in the next 30 days, higher than 99% of all CVEs. This Jenkins vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. 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. US federal agencies must remediate by 2025-10-23. Patch today.

Share this

Remediation#

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. (federal due date 2025-10-23)

Patch events

  1. Patch todayExploited (KEV)CISA due 2025-10-23

    CI/CDJenkins

    Remote Code ExecutionCVE-2017-1000353

    Why: Known exploited server software, exploitation is automatable, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2025-10-02CISA KEV
Ransomware useUnknownCISA KEV
EPSS (30-day exploitation probability)100% (100th pct)FIRST EPSS v2026.06.15
CVSS base score9.8 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationactiveCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

More from this vendor: all Jenkins vulnerabilities · recent KEV additions

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →