Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-53435: In Jenkins 2.567 and earlier, LTS 2.555.2 and earlier, it is possible for attackers to have Jenkins deserializ

56
This week
HIGH 8.8UPGRADE

CVE-2026-53435 is a high-severity flaw (CVSS 8.8) affecting jenkins. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 fi

Why this priority

  • High severity
  • EPSS top 1%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance53.1% (top 1%)
CISA exploited listNo
WeaknessCWE-502
Published2026-06-10
Last modified2026-10-26
Publisher (CNA): Jenkins Project · Vendor: jenkins

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

jenkins jenkins UPGRADE
Affected: < 2.555.3 · < 2.568
Fixed in: 2.555.3, 2.568
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy jenkins || rpm -q jenkins || jenkins --version
2. UPGRADE to 2.555.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade jenkins
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade jenkins
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Maven · org.jenkins-ci.main:jenkins-core · FIXED · 2.555.3 · vulnerable: < 2.555.3 · source
Set org.jenkins-ci.main:jenkins-core to 2.555.3 or later in pom.xml or build.gradle, then rebuild and redeploy.
Fedora 46 · selenium-manager · FIXED · 4.45.0-3.fc46 · FEDORA-2026-0af4ceb64a · source
sudo dnf upgrade --advisory=FEDORA-2026-0af4ceb64a
Fedora ELN · libdnf · FIXED · 0.76.0-2.eln159 · FEDORA-2026-dbd263e9d4 · source
sudo dnf upgrade --advisory=FEDORA-2026-dbd263e9d4

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-53435?

jenkins: upgrade to 2.555.3, 2.568. Exact commands for each OS are on this page.

Is CVE-2026-53435 being exploited?

CVE-2026-53435 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-53435 affect?

CVE-2026-53435 affects jenkins. Severity is high (CVSS 8.8). 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

How urgent is CVE-2026-53435?

Priority 56/100. High severity; EPSS top 1%: very likely to be exploited

Software pages

Jenkins vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.