Authenticated RCE on widely used Jenkins controller via plugin deserialization; impacts CI/CD infrastructure broadly and demands organization-wide attention.
CVE-2026-84670
Deserialization RCE in Jenkins Performance Plugin allowing controller code execution.
Is CVE-2026-84670 being exploited?
Not confirmed. CVE-2026-84670 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-84670?
CVE-2026-84670 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-84670?
Yes. A fix has been recorded for CVE-2026-84670. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84670 affect?
CVE-2026-84670 affects Jenkins Performance Plugin <= 1015.v09ca_52b_3370e, Jenkins controller / build server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84670?
Upgrade the Performance Plugin to the fixed release, restrict Item/Configure rights, and restart the controller.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with Item/Configure can trigger unsafe deserialization of cached reports to achieve arbitrary code execution on the Jenkins controller.
Immediate action required
- affected<= 1015.v09ca_52b_3370e
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.