CVE-2026-32613
CRITICALCVE-2026-32613 is a critical-severity (CVSS 9.9) vulnerability in io.spinnaker.echo:echo-pipelinetriggers. O3 Security confirms whether CVE-2026-32613 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling
Blast Radius
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.1 |
| ☕Maven | io.spinnaker.echo:echo-pipelinetriggers | ≥ 2025.4-0&&< 2025.4.2 | 2025.4.2 |
| ☕Maven | io.spinnaker.echo:echo-pipelinetriggers | all versions | 2025.3.2 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-32613 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-32613. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32613 in your dependencies?
O3 detects CVE-2026-32613 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.