CVE-2026-44795GHSA-C8Q4-9H32-2WW8
Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2025.4.4, 2026.0.3, 2025.3.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- spinnaker spinnaker
From 2025.4.0 · fixed in 2025.4.4; From 2026.0.0 · fixed in 2026.0.3; fixed in 2025.3.3
- io.spinnaker.rosco:rosco-coreMaven
fixed in 2025.3.3
- io.spinnaker.orca:orca-coreMaven
fixed in 2025.3.3
- io.spinnaker.rosco:rosco-coreMaven
From 2025.4.0 · fixed in 2025.4.4
- io.spinnaker.rosco:rosco-coreMaven
From 2026.0.0 · fixed in 2026.0.3
- io.spinnaker.orca:orca-coreMaven
From 2025.4.0 · fixed in 2025.4.4
- io.spinnaker.orca:orca-coreMaven
From 2026.0.0 · fixed in 2026.0.3