Quick answers
- Is CVE-2026-117618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117618 being exploited in the wild.
- How severe is CVE-2026-117618?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Jenkins Project Jenkins 2.587 and earlier, LTS 2.580.1 and earlier.
- Is there a fix for CVE-2026-117618?
- 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-117618 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-117618?
- Check whether you run Jenkins Project 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 HTTP endpoint for creating the first user account in Jenkins does not validate whether the setup wizard has been completed, creating a race condition. An unauthenticated attacker can POST to this endpoint simultaneously with the initial setup to instantiate an admin account. The vulnerability affects Jenkins 2.587 and earlier, and LTS 2.580.1 and earlier; the fix validates setup completion before allowing account creation.
Affected products
- Jenkins Project Jenkins 2.587 and earlier, LTS 2.580.1 and earlier
Timeline
- 2026-10-28: disclosed