CVE-2026-32604
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. 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.
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 confidenceThis is a command injection vulnerability in Spinnaker's clouddriver component where attackers can execute arbitrary commands on clouddriver pods through gitrepo artifact types. The vulnerability has a CVSS of 9.9 (CRITICAL) due to the ability to expose credentials, remove files, or inject resources into cloud environments.
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 installed Spinnaker versionRun 'hal version' if using Halmann, or check the Spinnaker deployment namespace: kubectl get deploy -n spinnaker -o jsonpath='{.items[*].metadata.labels.version}' or check the halo-deck or spin-deck deployment labelsAffected if The version is less than 2025.3.2, OR between 2025.4.0 and 2025.4.1 inclusive, OR between 2026.0.0 and 2026.0.0 inclusive
-
Locate the clouddriver componentRun kubectl get pods -n spinnaker | grep clouddriver to find clouddriver pods and note their exact version tags from the image nameAffected if The clouddriver image version matches the vulnerable Spinnaker versions above
-
Verify if gitrepo artifact provider is enabledCheck Spinnaker configuration: hal config artifact gitrepo enable (if using Halmann) or inspect the clouddriver YAML config for 'spinnaker.io/artifacts/gitrepo' in the provider settings under ~/.hal/default/profiles/ or in the Kubernetes configmapAffected if The gitrepo artifact provider is enabled (this is the attack surface for the vulnerability)
-
Inspect clouddriver pod runtimeRun kubectl describe pod <clouddriver-pod> -n spinnaker and check for any unexpected command entries, environment variables pointing to untrusted repositories, or custom scripts in the pod specAffected if Non-standard command arguments or environment variables related to git operations are present in the clouddriver pod definition
You are affected if your Spinnaker version falls within the vulnerable ranges AND the gitrepo artifact provider is enabled, allowing unauthenticated command injection in the clouddriver component.
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 to Spinnaker versions 2026.1.0, 2026.0.1, 2025.4.2, or 2025.3.2 which contain the patch, or temporarily disable gitrepo artifact types as a workaround until patching can be completed.
2026.1.0 (or 2026.0.1 / 2025.4.2 / 2025.3.2 depending on your current branch)
- 1. Identify your current Spinnaker deployment method (Halyard or Kubernetes Operator)
- 2. Identify your current Spinnaker version using 'hal version list' (Halyard) or checking the Operator CRD (Kubernetes Operator)
- 3. Determine the appropriate target version based on your current version branch: if < 2025.3.2, upgrade to 2025.3.2; if >= 2025.4.0 and < 2025.4.2, upgrade to 2025.4.2; if >= 2026.0.0 and < 2026.0.1, upgrade to 2026.0.1 or 2026.1.0
- 4. For Halyard deployments: run 'hal config version edit --version TARGET_VERSION' followed by 'hal deploy apply'
- 5. For Kubernetes Operator: update the SpinnakerService CR spec.spinnakerVersion to TARGET_VERSION and apply the changes
- 6. Verify the upgrade completed successfully by checking clouddriver pod logs and ensuring all components are healthy
- 7. As a secondary mitigation if immediate upgrade is not possible: disable gitrepo artifact types by setting 'artifacts.gitrepo.enabled: false' in your Spinnaker configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32604 — 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-32604 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