Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling
spinnaker
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.spinnaker.echo:echo-pipelinetriggers Maven |
|
|
spinnaker
| Product | Affected | Fixed in |
|---|---|---|
| io.spinnaker.echo:echo-pipelinetriggers Maven |
|
|
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.
From the CVE record · GitHub_M
Spinnaker Echo processes expected-artifact expressions without restricting access to trusted Java classes. A user who can supply those expressions can invoke commands and access files through the JVM. The input does not specify whether authentication or additional user interaction is required.
Teams running Spinnaker Echo before 2026.1.0, 2026.0.1, 2025.4.2, or 2025.3.2 should check their version, including deployments using the affected Maven package io.spinnaker.echo:echo-pipelinetriggers.