CVE-2026-32604: critical vulnerability in spinnaker
Spinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 10epss 0.6%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
spinnaker · spinnakerRelated CVEs — spinnaker
In the same product, most dangerous first.
CVE-2021-43832CRITICALImproper Access Control in spinnakerEPSS 2.7%CVE-2026-55175HIGHSpinnaker: Improper yaml processing on kustomize bake operationsEPSS 1.1%CVE-2026-44795HIGHSpinnaker: Non-safe yaml deserialization allowing RCE when using specific typesEPSS 1.0%CVE-2022-23506MEDIUMSpinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer buildsEPSS 0.6%CVE-2026-32613CRITICALSpinnaker vulnerable to RCE via expression parsing due to unrestricted context handlingEPSS 0.6%CVE-2023-39348MEDIUMImproper log output when using GitHub Status Notifications in spinnakerEPSS 0.4%
References
https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1https://github.com/spinnaker/spinnaker/security/advisories/GHSA-x3j7-7pgj-h87rhttps://zeropath.com/blog/spinnaker-rce-production-compromise