CVE-2026-32604 — Spinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths
Spinnaker is an open source, multi-cloud continuous delivery platform. In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, a bad actor can execute arbitrary commands very simply on the clouddriver pods. This can expose credentials, remove files, or inject resources easily. Versions 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2 contain a patch. As a workaround, disable the gitrepo artifact types.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.8% (30-day exploitation probability)+8
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — github.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linuxfoundation Spinnaker, Spinnaker Spinnaker).
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linuxfoundation | Spinnaker | < 2025.3.2≥ 2025.4.0 and < 2025.4.2≥ 2026.0.0 and < 2026.0.1 | Vulnerable | NIST National Vulnerability Database |
| Spinnaker | Spinnaker | version < 2026.0.1version < 2025.4.2version < 2025.3.2version < 2026.1.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 3.1 | Critical | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
| 9.9 | CVSS 3.1 | Critical | 3.1 | 6.0 | security-advisories@github.com via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.77%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · spinnaker/spinnaker
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 9.9
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
5 on the record
- github.com/spinnaker/spinnaker/security/advisories/GHSA-x3j7-7pgj-h87r
- github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2
- github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2
- zeropath.com/blog/spinnaker-rce-production-compromise
- github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-55175 Spinnaker: Improper yaml processing on kustomize bake operations Jul 10, 2026
- High CVE-2026-44795 Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types Jul 10, 2026
- Critical CVE-2026-32613 Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling Apr 20, 2026
- Medium CVE-2025-61916 Spinnaker vulnerable to SSRF due to improper restrictions on http from user input Jan 5, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-32604 is "Spinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths", rated Critical. It affects Spinnaker (Linuxfoundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.9 describes technical severity. EPSS 0.77% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.