cve.bz

CVE-2026-32613 linuxfoundation spinnaker: Code Injection

9.9 criticalEPSS 0.6%Fix available

Critical (9.9) in linuxfoundation spinnaker. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in io.spinnaker.echo:echo-pipelinetriggers 2025.3.2, 2025.4.2, 2026.0.1.

On this page
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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32613 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32613?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32613?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32613 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:spinnakerbefore 2025.3.2
linuxfoundation:spinnakerfrom 2025.4.0 before 2025.4.2
linuxfoundation:spinnakerfrom 2026.0.0 before 2026.0.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-69rw-45wj-g4v6Mavenio.spinnaker.echo:echo-pipelinetriggers>=2026.0-0 <2026.0.12026.0.1
GHSA-69rw-45wj-g4v6Mavenio.spinnaker.echo:echo-pipelinetriggers>=2025.4-0 <2025.4.22025.4.2
GHSA-69rw-45wj-g4v6Mavenio.spinnaker.echo:echo-pipelinetriggers<2025.3.22025.3.2

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON