### 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!
Update io.spinnaker.orca:orca-core to 2025.3.3; io.spinnaker.orca:orca-core to 2025.4.4; io.spinnaker.orca:orca-core to 2026.0.3; io.spinnaker.rosco:rosco-core to 2025.3.3; io.spinnaker.rosco:rosco-core to 2025.4.4; io.spinnaker.rosco:rosco-core to 2026.0.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSpinnaker has uon-safe yaml deserialization, allowing RCE when using specific types affects io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.rosco:rosco-core (maven), io.spinnaker.rosco:rosco-core (maven), io.spinnaker.rosco:rosco-core (maven). Severity is high. ### 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 coding agents often install or upgrade packages automatically in maven. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package |
|---|
### 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!
Update io.spinnaker.orca:orca-core to 2025.3.3; io.spinnaker.orca:orca-core to 2025.4.4; io.spinnaker.orca:orca-core to 2026.0.3; io.spinnaker.rosco:rosco-core to 2025.3.3; io.spinnaker.rosco:rosco-core to 2025.4.4; io.spinnaker.rosco:rosco-core to 2026.0.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanSpinnaker has uon-safe yaml deserialization, allowing RCE when using specific types affects io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.rosco:rosco-core (maven), io.spinnaker.rosco:rosco-core (maven), io.spinnaker.rosco:rosco-core (maven). Severity is high. ### 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 coding agents often install or upgrade packages automatically in maven. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package |
|---|
| Affected range |
|---|
| Fixed version |
|---|
| io.spinnaker.orca:orca-coremaven | <2025.3.3 | 2025.3.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 |
| io.spinnaker.rosco:rosco-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 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Affected range |
|---|
| Fixed version |
|---|
| io.spinnaker.orca:orca-coremaven | <2025.3.3 | 2025.3.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 |
| io.spinnaker.rosco:rosco-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 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard