Quick answers
- Is CVE-2026-84656 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84656 being exploited in the wild.
- How severe is CVE-2026-84656?
- Medium severity, with a CVSS score of 4.3, published 2 September 2026.
- Which products and versions are affected?
- Jenkins 2.579 and earlier, LTS 2.568.2 and earlier.
- Is there a fix for CVE-2026-84656?
- A patch was published on 2026-09-02: Jenkins 2.580, LTS 2.568.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84656 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84656?
- 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.579 and earlier (LTS 2.568.2 and earlier) fails to properly validate permissions when exposing build parameter metadata. An attacker with Item/Read permission on at least one job can leverage this missing permission check to enumerate and read parameter names and values from jobs outside their authorization scope. The vulnerability is network-accessible and does not require authentication beyond the minimum Item/Read permission already held on one accessible job. Exploitation could expose API keys, passwords, and other sensitive configuration data stored in build parameters. Jenkins 2.580 and LTS 2.568.3 include a fix restricting parameter access based on proper job-level authorization checks.
Affected products
- Jenkins Jenkins 2.579 and earlier, LTS 2.568.2 and earlier
Timeline
- 2026-09-02: disclosed
- 2026-09-02: patched: Jenkins 2.580, LTS 2.568.3