Affects widely used Jenkins; CSRF token disclosure enables attackers to act as authenticated users and modify CI/CD configurations — high impact across organizations.
CVE-2026-84649
Jenkins endpoint leaks CSRF token in served JS enabling request forgery.
Is CVE-2026-84649 being exploited?
Not confirmed. CVE-2026-84649 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-84649?
CVE-2026-84649 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84649?
Yes. A fix has been recorded for CVE-2026-84649. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84649 affect?
CVE-2026-84649 affects Jenkins 2.447 - 2.579, Jenkins LTS 2.452.1 - 2.568.2, Stapler 1839.ved17667b_a_eb_5 - 2107.v8dfcb_e8ed317 (excl 2088.2093.vd7c3e58008a_6). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84649?
Upgrade Jenkins to fixed versions >2.579 or LTS >2.568.2 immediately; follow advisory mitigations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Same-site attacker can obtain user's CSRF crumb and perform actions as that user, including admin operations, job/config changes, and plugin installs.
Immediate action required