Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types
spinnaker
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.spinnaker.rosco:rosco-core Maven |
|
|
| io.spinnaker.orca:orca-core Maven |
spinnaker
| Product | Affected | Fixed in |
|---|---|---|
| io.spinnaker.rosco:rosco-core Maven |
|
|
| io.spinnaker.orca:orca-core Maven |
< 2025.3.3≥ 2025.4.0 · < 2025.4.4≥ 2026.0.0 · < 2026.0.3
|
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.
From the CVE record · GitHub_M
Unsafe YAML processing in Spinnaker’s CloudFormation deployments and CloudFoundry baking can bypass safe deserialization. A non-safe constructor can load arbitrary Java classes, leading to remote code execution. The input does not specify authentication requirements or whether user interaction is needed.
Teams running Spinnaker with affected Maven versions of rosco-core or orca-core should check their installations: versions below 2025.3.3, 2025.4.0 through 2025.4.3, or 2026.0.0 through 2026.0.2.