CVE-2026-32613
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpinnaker 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Echo service in Spinnaker uses Spring Expression Language (SPeL) to process expected artifacts but failed to restrict the expression evaluation context to a whitelist of trusted classes. This allowed arbitrary Java class instantiation and method invocation, providing full JVM access and enabling remote code execution, command execution, and file system access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2025.3.2>= 2025.4.0, < 2025.4.2>= 2026.0.0, < 2026.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Echo service is deployedCheck for running Echo pods or processes in the Spinnaker namespace. Common commands: 'kubectl get pods -n spinnaker | grep echo' or 'docker ps | grep spin-echo'Affected if Echo service is not found in the environment (not affected)
-
Determine Echo service versionRetrieve the Echo service version from the container image tag, pod labels, or API endpoint. For Kubernetes: 'kubectl get pods -n spinnaker -l app=spin-echo -o jsonpath="{.items[*].spec.containers[*].image}"'Affected if Version cannot be determined or is empty
-
Compare version against affected rangesCompare the installed Echo version to the affected ranges: < 2025.3.2, >= 2025.4.0 and < 2025.4.2, >= 2026.0.0 and < 2026.0.1. If version falls into any of these ranges, the environment is vulnerable.Affected if Installed version matches any affected range (less than 2025.3.2, between 2025.4.0-2025.4.1, or between 2026.0.0-2026.0.0)
-
Check if expected artifacts feature is enabledInspect Echo service configuration for expected artifact processing. Check Spinnaker configuration files (usually in halconfig or spin-config) for 'artifact' or 'expected-artifact' references, or query the Echo API endpoint if accessible.Affected if Expected artifacts feature is configured and Echo is processing artifact definitions
-
Verify Echo service is exposed or accessibleConfirm Echo service network accessibility. Check Kubernetes service exposure, firewall rules, or whether Echo API ports (typically 8089 or configured port) are reachable from untrusted networks.Affected if Echo service API is network-accessible from untrusted sources
Environment is affected if Echo service is running with a version matching the affected ranges AND the expected artifacts feature is in use, especially if Echo is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2025.3.22025.4.22026.0.1
Upgrade Echo to versions 2026.1.0, 2026.0.1, 2025.4.2, or 2025.3.2 which contain the patch restricting SPeL to trusted classes. If immediate upgrade is not possible, disable the Echo service as a workaround.
2026.1.0 (latest fixed release, or appropriate version for your branch: 2025.3.2, 2025.4.2, or 2026.0.1)
- 1. Take a backup of your current Spinnaker configuration and database
- 2. Upgrade Spinnaker to version 2026.1.0 (or at minimum: 2025.3.2 if on 2025.3.x branch, 2025.4.2 if on 2025.4.x branch, or 2026.0.1 if on 2026.0.x branch)
- 3. Verify the Echo service starts successfully after upgrade
- 4. Test that pipeline executions with expected artifacts function correctly
- 5. Confirm the SPeL restriction is in place by verifying only trusted classes are accessible in artifact expression contexts
- 6. Monitor logs for any errors or unauthorized access attempts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32613 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data