Skip to content
major vulnerability· requires attention

RCE via CSRF against Jenkins controller JVM can fully compromise CI/CD infrastructure used widely by organizations.

Applications

CVE-2026-70432

8.8
High
EPSS 0.21%Patch availableAug 6, 2026

CSRF in Jenkins Multijob Plugin enables remote code execution on controller

common questions

Is CVE-2026-70432 being exploited?

Not confirmed. CVE-2026-70432 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.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-70432?

CVE-2026-70432 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-70432?

Yes. A fix has been recorded for CVE-2026-70432. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-70432 affect?

CVE-2026-70432 affects Jenkins Multijob Plugin (<= 669.v9d96a_d9c71b_0), Jenkins controller (JVM). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70432?

Upgrade or remove Multijob Plugin; restrict controller access and enable CSRF protections.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Jenkins Multijob Plugin (<= 669.v9d96a_d9c71b_0)Jenkins controller (JVM)
impact

CSRF allows remote attackers to execute arbitrary code in the Jenkins controller JVM, enabling full server compromise and pipeline tampering.

action required

Immediate action required

affected versions
Jenkins Project Jenkins Multijob Plugin
  • affected<= 669.v9d96a_d9c71b_0

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free