Deserialization in Jenkins

CVE-2026-53435

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.022 (82.1th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 82nd percentile — 82.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-53435: held from 0.022 to 0.022.

EPSS over last 30 days · oldest: 0.022 · newest: 0.022 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2026-53435?
CVE-2026-53435 is a high-severity vulnerability in Jenkins, classified under Deserialization of Untrusted Data. CVSS score: 8.8/10. Published 2026-06-10.
How severe is CVE-2026-53435?
High severity. CVSS v3 base score is 8.8 out of 10.
Is CVE-2026-53435 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.