How severe is CVE-2026-117619?

CVE-2026-117619 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-117619?

CVE-2026-117619 affects the following products: jenkins jenkins.

How do I patch CVE-2026-117619?

Apply the jenkins jenkins security patch or hotfix for CVE-2026-117619 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2026-117619 across my infrastructure?

Inventory every jenkins jenkins deployment and check each version against the affected-products list above.

How do I mitigate CVE-2026-117619 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2026-117619 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-117619 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-117619?

CVE-2026-117619 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Which products and versions are affected by CVE-2026-117619?

CVE-2026-117619 affects jenkins jenkins. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-117619 published, and has it been updated?

CVE-2026-117619 was published on October 28, 2026 and was last updated on November 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

HIGH severity

CVE-2026-117619 — Jenkins

HIGH

CVE-2026-117619 is a high-severity (CVSS 8.1) vulnerability in jenkins jenkins. A fix is available — see the affected versions and patch details below.

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…

Published

Oct 28, 2026

Updated

Nov 2, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Description

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 Products

1 product · 2 configurations

Application

jenkinsjenkins

< 2.588

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every jenkins jenkins deployment and check each version against the affected-products list above.
Fix
Apply the jenkins jenkins security patch or hotfix for CVE-2026-117619 on the affected version, following the vendor advisory for your exact build.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2026-117619 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works