Affects Jenkins, a widely used CI server; deserialization flaw can enable RCE or privilege escalation and disrupt build/deploy pipelines across organizations.
CVE-2026-84650
Jenkins deserialization flaw lets attackers set transient fields via config updates.
Is CVE-2026-84650 being exploited?
Not confirmed. CVE-2026-84650 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-84650?
CVE-2026-84650 is rated High. 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-84650?
Yes. A fix has been recorded for CVE-2026-84650. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84650 affect?
CVE-2026-84650 affects Jenkins 2.579 and earlier, Jenkins LTS 2.568.2 and earlier, Jenkins CI server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84650?
Upgrade Jenkins to the fixed release, restrict config-update access, and apply vendor mitigations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers able to submit Jenkins configuration can set transient fields during deserialization, enabling data tampering, privilege escalation, or remote code execution.
Immediate action required