Quick answers
- Is CVE-2026-84651 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84651 being exploited in the wild.
- How severe is CVE-2026-84651?
- Medium severity, with a CVSS score of 6.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-84651?
- A patch was published on 2026-09-02: 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-84651 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84651?
- 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
The vulnerability exists in Jenkins REST API and CLI endpoints for agent configuration that fail to validate that submitted XML documents target only the intended agent. An attacker with Agent/Configure permission on one agent can specify a different agent's name in the submitted XML, causing the configuration update to overwrite the target agent's settings instead. This allows an attacker to extract the inbound agent secret and environment variables from the compromised agent. No authentication bypass is required; the vulnerability requires existing Agent/Configure permissions on at least one agent. Patches are available in Jenkins 2.580 and LTS 2.568.3.
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 and LTS 2.568.3