Quick answers
- Is CVE-2026-117614 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117614 being exploited in the wild.
- How severe is CVE-2026-117614?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Jenkins 2.587 and earlier, LTS 2.580.1 and earlier.
- Is there a fix for CVE-2026-117614?
- Yes: fixed in Jenkins 2.588, LTS 2.580.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117614 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-117614?
- 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.
How to fix
- Fixed in: Jenkins 2.588, LTS 2.580.2
Technical details
For backward compatibility, Jenkins 2.587 and earlier converts launch commands from older agent configurations into Command Agent Launcher Plugin launchers without verifying administrator approval. An attacker with Agent/Configure permission can exploit this to execute arbitrary code in the Jenkins controller JVM context. The fix in Jenkins 2.588 and LTS 2.580.2 removes this automatic conversion entirely, eliminating the bypass vector.
Affected products
- Jenkins Jenkins 2.587 and earlier, LTS 2.580.1 and earlier
Timeline
- 2026-10-28: disclosed