CVE-2026-53435
Jenkins Deserialization Vulnerability Leads to Remote Code Execution
Description
In Jenkins 2.567 and earlier, LTS 2.555.2 and earlier, it is possible for attackers to have Jenkins deserialize arbitrary types defined in Jenkins core or plugins from an attacker-controlled `config.xml` submission in a way that allows them to handle HTTP requests afterwards. This can be used to impersonate any user and send HTTP requests on their behalf, up to and including use of the Script Console to run arbitrary code, or to read arbitrary files from the Jenkins controller.
INFO
Published Date :
June 10, 2026, 1:05 p.m.
Last Modified :
June 10, 2026, 1:05 p.m.
Remotely Exploit :
No
Source :
jenkins
Affected Products
The following products are affected by CVE-2026-53435
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update Jenkins to version 2.568 or later.
- Update LTS Jenkins to version 2.555.3 or later.
- Restrict XML configuration submissions to trusted users.
- Review Jenkins security configuration.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53435 vulnerability anywhere in the article.