CVE-2026-44795
HighCVSS 8.8Exploitation Probability (EPSS)
Elevated risk59th percentile - higher than 59% of all known CVEs
Summary
A vulnerability in Spinnaker allows remote code execution through unsafe YAML processing when using CloudFormation or CloudFoundry. The use of a non-safe constructor enables arbitrary Java class loading, leading to remote code execution.
Risk Assessment
An attacker can remotely execute arbitrary code on the Spinnaker server, potentially leading to full compromise of the continuous delivery platform and access to managed cloud resources.
Recommendation
Immediately upgrade Spinnaker to versions 2026.1.0, 2026.0.3, 2025.4.4, or 2025.3.3. Until patched, restrict access to interfaces using CloudFormation and CloudFoundry.
Other vulnerabilities in Spinnaker
See all- CVE-2026-55175High
Spinnaker prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 contains a vulnerability in Kustomize bake operations that allows unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes.
- CVE-2023-39348Medium
Spinnaker, an open source multi-cloud continuous delivery platform, has a logging issue where GitHub status is always logged in full. This may lead to the exposure of GitHub tokens in the logging system.
Original NVD description (English source)
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 constructor allows arbitrary loading of Java classes, leading to remote code execution. This issue is fixed in versions 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3.