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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HJenkins
APPJenkins≤ 2.56≤ 2.46.1Oracle Communications Cloud Native Core Automated Test Suite
APPOracle1.9.0
CISA KEV — detailsi
- Vendori
- Jenkins
- Producti
- Jenkins
- Added to KEVi
- October 2, 2025
- Remediation deadline (US Federal)i
- October 23, 2025(overdue)
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.
Related vulnerabilities
Jenkins CLI – odczyt dowolnych plików przez path traversal bez uwierzytelnienia
Spring4Shell — RCE przez data binding w Spring MVC/WebFlux na JDK 9+
RCE w Spring Cloud Function poprzez złośliwy SpEL routing-expression
RCE w Jenkins — nieuprawnione wywołanie metod przez Stapler framework
Stored XSS w Jenkins poprzez wersję wymaganą przez wtyczkę