GHSA-69rw-45wj-g4v6
Spinnaker: RCE via expression parsing due to unrestricted context handling
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | io.spinnaker.echo:echo-pipelinetriggers | >= 2026.0-0, < 2026.0.1 | 2026.0.1 |
| Maven | io.spinnaker.echo:echo-pipelinetriggers | >= 2025.4-0, < 2025.4.2 | 2025.4.2 |
| Maven | io.spinnaker.echo:echo-pipelinetriggers | < 2025.3.2 | 2025.3.2 |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-69rw-45wj-g4v6
- https://nvd.nist.gov/vuln/detail/CVE-2026-32613
- https://github.com/spinnaker/spinnaker
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1
- https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.2
- https://zeropath.com/blog/spinnaker-rce-production-compromise