Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2026.0.1, 2025.4.2, 2025.3.2, 2026.1.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- spinnaker spinnaker
fixed in 2026.0.1; fixed in 2025.4.2; fixed in 2025.3.2; fixed in 2026.1.0
- io.spinnaker.echo:echo-pipelinetriggersMaven
From 2026.0-0 · fixed in 2026.0.1
- io.spinnaker.echo:echo-pipelinetriggersMaven
From 2025.4-0 · fixed in 2025.4.2
- io.spinnaker.echo:echo-pipelinetriggersMaven
fixed in 2025.3.2