Jenkins 2.587 and earlier, LTS 2.580.1 and earlier allows requests authenticated using HTTP Basic authentication
Source GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 19:44 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, restrict API token exposure and monitor for unauthorized access. Consider disabling HTTP Basic authentication or the "remember me" feature if feasible.
Description
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where HTTP Basic authentication requests, including those using an API token, can obtain a "remember me" cookie. This allows attackers who have obtained a user's API token to maintain access to Jenkins via the "remember me" cookie even after the API token is revoked or expires.