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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-32613 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 |
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, 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
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32613 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2026-32613 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.