Spinnaker vulnerabilities
We track 5 vulnerabilities in Spinnaker products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on July 10, 2026.
Latest Spinnaker vulnerabilities
- 7.5 High severity
spinnaker: Deserialization of Untrusted Data
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead
- 8.8 High severity
spinnaker: Use of Externally-Controlled Input to Select Classes or Code
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3, unsafe YAML processing bypasses safe deserialization when using CloudFormation deployments or CloudFoundry baking. The use of a non-safe
- 9.9 Critical severity
spinnaker: Improper Control of Generation of Code
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
- 9.9 Critical severity
Spinnaker is an open source, multi-cloud continuous delivery platform.
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, o
- 7.5 High severity
spinnaker: Insertion of Sensitive Information into Log File
Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes, and Spinnaker's Rosco microservice produces machine images. Rosco prior to versions 1.29.2, 1.28.4, and 1.27.3 does not property mask secrets generated via pa