Quick answers
- Is CVE-2026-84653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84653 being exploited in the wild.
- How severe is CVE-2026-84653?
- Low severity, with a CVSS score of 3.5, published 2 September 2026.
- Which products and versions are affected?
- Jenkins 2.421 through 2.579, LTS 2.426.1 through 2.568.2.
- Is there a fix for CVE-2026-84653?
- A patch was published on 2026-09-02: Fixed in Jenkins 2.580 and LTS 2.568.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84653 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84653?
- Check whether you run Jenkins at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Jenkins 2.421–2.579 and LTS 2.426.1–2.568.2 fail to enforce proper permission checks on the Appearance configuration page. The vulnerability allows attackers holding Overall/Manage permission to access and modify Appearance options beyond their intended authorization scope. This is a logic flaw in permission validation rather than an authentication bypass. The issue was fixed in Jenkins 2.580 and LTS 2.568.3. No authentication bypass is required; the attacker must already possess Overall/Manage rights.
Affected products
- Jenkins Jenkins 2.421 through 2.579, LTS 2.426.1 through 2.568.2
Timeline
- 2026-09-02: disclosed
- 2026-09-02: patched: Fixed in Jenkins 2.580 and LTS 2.568.3