GHSA-c8q4-9h32-2ww8
Spinnaker has non-safe yaml deserialization, allowing RCE when using specific types
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | io.spinnaker.rosco:rosco-core | < 2025.3.3 | 2025.3.3 |
| Maven | io.spinnaker.orca:orca-core | < 2025.3.3 | 2025.3.3 |
| Maven | io.spinnaker.rosco:rosco-core | >= 2025.4.0, < 2025.4.4 | 2025.4.4 |
| Maven | io.spinnaker.rosco:rosco-core | >= 2026.0.0, < 2026.0.3 | 2026.0.3 |
| Maven | io.spinnaker.orca:orca-core | >= 2025.4.0, < 2025.4.4 | 2025.4.4 |
| Maven | io.spinnaker.orca:orca-core | >= 2026.0.0, < 2026.0.3 | 2026.0.3 |
Details
As written in the advisory (Markdown source, shown as plain text).
### 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!
References
External links from the advisory. They lead to third-party sites.
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-c8q4-9h32-2ww8
- https://nvd.nist.gov/vuln/detail/CVE-2026-44795
- https://github.com/spinnaker/spinnaker/commit/4cbe1d5fea9df573aadfd8b093fb4b594b354ee5
- https://github.com/spinnaker/spinnaker/commit/e57c0db4584b398473a7bbb19402ce6c1e89b627
- https://github.com/spinnaker/spinnaker/commit/f69d7b534d068ed74d0d3a1fbf17e2c945d36e5e
- https://github.com/spinnaker/spinnaker