Quick answers
- Is CVE-2026-117622 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117622 being exploited in the wild.
- How severe is CVE-2026-117622?
- 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-117622?
- 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-117622 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-117622?
- 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
The vulnerability exists in how Jenkins processes exceptions sent from agents to the controller. Agents can send exceptions that implement the Stapler HttpResponse interface, which are not properly sanitized before being rendered in the controller's web responses, enabling XSS. Exploitation requires control of an agent process and does not require authentication at the Jenkins controller level. A successful attack allows arbitrary JavaScript execution in the context of an administrator's browser session.
Affected products
- Jenkins Jenkins 2.587 and earlier, LTS 2.580.1 and earlier
Timeline
- 2026-10-28: disclosed