CVE-2026-32613
In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, unlike orca, it was NOT restricting that context to a set of trusted classes, but allowing FULL JVM access.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.55%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
Spinnaker is an open source, multi-cloud continuous delivery platform. Echo like some other services, uses SPeL (Spring Expression Language) to process information - specifically around expected artifacts. In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, unlike orca, it was NOT restricting that context to a set of trusted classes, but allowing FULL JVM access. This enabled a user to use arbitrary java classes which allow deep access to the system. This enabled the ability to invoke commands, access files, etc. Versions 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2 contain a patch. As a workaround, disable echo entirely.
- CVSS 3.1
- 9.9 CRITICALCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- EPSS
- 0.55% probability · 45th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-94
- Affected
- linuxfoundation/spinnaker
- Source
- security-advisories@github.com
References
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2Product, Release Notes
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2Product, Release Notes
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1Product, Release Notes
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-69rw-45wj-g4v6Mitigation, Vendor Advisory
- https://zeropath.com/blog/spinnaker-rce-production-compromise
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.