Jenkins Project · Jenkins · published 2026-06-10
CVE-2026-53435
This week EPSS 51% chance of exploitation in 30 days, with critical impact.
CVE-2026-53435 is not known to be exploited in the wild. EPSS estimates a 51.2% chance of exploitation in the next 30 days, higher than 98% of all CVEs. This Jenkins vulnerability: CVSS 8.8 (v3.1), a successful attack gives total control of the component. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Patch events
CI/CDJenkins
Jenkins: Jenkins Security Advisory 2026-06-10
Why: CVE-2026-53435: EPSS 51% chance of exploitation in 30 days, with critical impact.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 51% (99th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Jenkins Project Jenkins
2.568to before*(unaffected)2.555.3to before2.555.*(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.