CVE-2026-117619: Jenkins
Affects JenkinsSource CVE Database V5
Not known to be exploited.
Data as of 28 Oct 2026, 17:22 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins ProjectJenkins | Affected– | Fixed in– |
AI-suggested
Until a fix is available, users should consider revoking API tokens carefully and monitoring for unusual access patterns.
Description
A vulnerability in Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, allows attackers who have obtained a user's API token to retain access to Jenkins via a "remember me" cookie even after the API token is revoked or expires. This occurs because requests authenticated using HTTP Basic authentication can obtain this cookie, which persists access beyond token validity.