RCE in Spinnaker via unsafe SPeL affects a widely used CI/CD platform; high risk across orgs.
CVE-2026-32613
RCE in Spinnaker due to unrestricted SPeL in older builds.
Is CVE-2026-32613 being exploited?
Not confirmed. CVE-2026-32613 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.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-32613?
CVE-2026-32613 is rated Critical with a CVSS score of 9.9. 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-32613?
Yes. A fix has been recorded for CVE-2026-32613. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32613 affect?
CVE-2026-32613 affects Spinnaker (versions prior to 2026.1.0, 2026.0.1, 2025.4.2, 2025.3.2). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32613?
Upgrade to patched versions; disable echo as workaround.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via SPeL: arbitrary Java class access enables commands and file access on Spinnaker server.
Patch when possible
- affected< 2026.0.1
- affected< 2025.4.2
- affected< 2025.3.2
- affected< 2026.1.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.