CVE-2026-32613 — echo-pipelinetriggers
CRITICALCVE-2026-32613 is a critical-severity (CVSS 9.9) Code Injection vulnerability in io.spinnaker.echo:echo-pipelinetriggers. A fix is available for io.spinnaker.echo:echo-pipelinetriggers — see the affected versions and patch details below.
Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32613.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.spinnaker.echo:echo-pipelinetriggers☕io.spinnaker.echo:echo-pipelinetriggers☕io.spinnaker.echo:echo-pipelinetriggersReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.spinnaker.echo:echo-pipelinetriggers | ≥ 2026.0-0&&< 2026.0.1 | 2026.0.1io.spinnaker.echo:echo-pipelinetriggers:2026.0.1 |
| ☕Maven | io.spinnaker.echo:echo-pipelinetriggers | ≥ 2025.4-0&&< 2025.4.2 | 2025.4.2io.spinnaker.echo:echo-pipelinetriggers:2025.4.2 |
| ☕Maven | io.spinnaker.echo:echo-pipelinetriggers | all versions | 2025.3.2io.spinnaker.echo:echo-pipelinetriggers:2025.3.2 |
Affected Products
spinnakerlinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spinnaker.echo:echo-pipelinetriggers, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.spinnaker.echo:echo-pipelinetriggers to 2026.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32613 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-32613 in your dependencies?
Find it across Maven, including transitive dependencies.