Spinnaker has uon-safe yaml deserialization, allowing RCE when using specific types
Description
Impact
There's an unsafe YAML processing vulnerability that bypasses safe deserialization. This impacts users when when performing: * CloudFormation deployments * CloudFoundry Baking
The usage of a non-safe constructor use allows arbitrary loading of Java classes leading to RCE.
### Patches 2025.3.3, 2026.0.3 and 2025.4.4.
Workarounds
Disable the CloudFormation system and cloudfoundry baking operations.
Resources
Join Spinnaker on Slack for more information!
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
io.spinnaker.rosco:rosco-coreMaven | < 2025.3.3 | 2025.3.3 |
io.spinnaker.orca:orca-coreMaven | < 2025.3.3 | 2025.3.3 |
io.spinnaker.rosco:rosco-coreMaven | >= 2025.4.0, < 2025.4.4 | 2025.4.4 |
io.spinnaker.rosco:rosco-coreMaven | >= 2026.0.0, < 2026.0.3 | 2026.0.3 |
io.spinnaker.orca:orca-coreMaven | >= 2025.4.0, < 2025.4.4 | 2025.4.4 |
io.spinnaker.orca:orca-coreMaven | >= 2026.0.0, < 2026.0.3 | 2026.0.3 |
Affected products
1Patches
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.