CVE-2026-117619: Jenkins Jenkins vulnerability

Published Oct 28, 2026
·
Updated

Jenkins 2.587 and earlier, LTS 2.580.1 and earlier allows requests authenticated using HTTP Basic authentication, including with an API token, to obtain a "remember me" cookie, allowing attackers who have obtained a user's API token to retain access to Jenkins using a "remember me" cookie after the API token is revoked or expires.

Affected Software

1 affected component
Jenkins Jenkins<=2.587, <=2.580.1

Event History

Oct 28, 2026
CVE Published
via MITRE·04:48 PM
Data Sourced
via MITRE·04:48 PM
Description

Frequently Asked Questions

1

Who can exploit this issue?

An attacker must already possess a Jenkins user's API token and be able to authenticate to Jenkins using HTTP Basic authentication. The issue lets them convert that token-based access into a persistent "remember me" cookie.

2

What happens if the compromised API token is revoked or expires?

Revoking or allowing the API token to expire may not end the attacker's access if they already obtained a "remember me" cookie. The cookie can retain their Jenkins access after the token is no longer valid.

3

Which Jenkins installations are affected?

Jenkins 2.587 and earlier, and Jenkins LTS 2.580.1 and earlier, are affected when requests can authenticate with HTTP Basic authentication, including API-token authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203