CVE-2026-84645: In Jenkins 2.579 and earlier, LTS 2.568.2 and earlier, objects of types marked as storing their configuration

Q: How do I fix CVE-2026-84645?

jenkins: upgrade to 2.568.3, 2.580. Exact commands for each OS are on this page.

Q: Is CVE-2026-84645 being exploited?

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

Q: What does CVE-2026-84645 affect?

CVE-2026-84645 affects jenkins. Severity is high (CVSS 8.8). In Jenkins 2.579 and earlier, LTS 2.568.2 and earlier, objects of types marked as storing their configuration in independent top-level configuration files in Jenkins (such as the global configuration and jobs) can appear as nested field val

This month

HIGH 8.8UPGRADE

CVE-2026-84645 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.579 and earlier, LTS 2.568.2 and earlier, objects of types marked as storing their configuration in independent top-level configuration files in Jenkins (such as the global configuration and jobs) can appear as nested field values in user-submitted `config.xml` documents and subsequently handle HTTP requests via Stapler, resulting in remote code execution.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-94, CWE-915
Published	2026-09-02
Last modified	2026-09-11

Publisher (CNA): Jenkins Project · Vendor: jenkins

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

Am I affected?

Timeline

2026-09-02 16:17 UTCPublished CVE record published
2026-09-11 21:15 UTCUpdated Record last modified

jenkins jenkins UPGRADE

Affected: < 2.568.3 · < 2.580

Fixed in: 2.568.3, 2.580

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.568.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.

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-84645?

jenkins: upgrade to 2.568.3, 2.580. Exact commands for each OS are on this page.

Is CVE-2026-84645 being exploited?

CVE-2026-84645 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-84645 affect?

CVE-2026-84645 affects jenkins. Severity is high (CVSS 8.8). In Jenkins 2.579 and earlier, LTS 2.568.2 and earlier, objects of types marked as storing their configuration in independent top-level configuration files in Jenkins (such as the global configuration and jobs) can appear as nested field val

How urgent is CVE-2026-84645?

Priority 45/100. High severity

Software pages

Jenkins vulnerabilities

Related CVEs

CVE-2026-53435 HIGH 8.8 UPGRADE In Jenkins 2.567 and earlier, LTS 2.555.2 and earlier, it is possible for attackers to have Jenkins deserializ
CVE-2026-53437 MEDIUM 4.3 UPGRADE Jenkins 2.567 and earlier, LTS 2.555.2 and earlier improperly determines that a redirect URL after login is le
CVE-2026-53442 MEDIUM 5.3 UPGRADE Jenkins 2.567 and earlier, LTS 2.555.2 and earlier does not encrypt secrets from POST config.xml submissions b
CVE-2026-53441 MEDIUM 5.4 UPGRADE Jenkins 2.483 through 2.567 (both inclusive), LTS 2.492.1 through 2.555.2 (both inclusive) does not escape the
CVE-2026-53436 MEDIUM 4.3 UPGRADE Jenkins 2.567 and earlier, LTS 2.555.2 and earlier improperly determines that a redirect URL after login is le

References

← Back to latest CVEs