CVE-2026-44795: Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types

Published Jun 22, 2026
·
Updated

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!

Other sources

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.

MITRE

Affected Software

9 affected componentsFixes available
maven/io.spinnaker.orca:orca-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.rosco:rosco-core>=2026.0.0<2026.0.3
2026.0.3
maven/io.spinnaker.rosco:rosco-core>=2025.4.0<2025.4.4
2025.4.4
maven/io.spinnaker.orca:orca-core<2025.3.3
2025.3.3
maven/io.spinnaker.rosco:rosco-core<2025.3.3
2025.3.3
linuxfoundation Spinnaker<2025.3.3
linuxfoundation Spinnaker>=2025.4.0<2025.4.4
linuxfoundation Spinnaker>=2026.0.0<2026.0.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.spinnaker.orca:orca-core to a version that resolves this vulnerability.

    Fixed in 2026.0.3
  2. Upgrade

    Upgrade maven/io.spinnaker.orca:orca-core to a version that resolves this vulnerability.

    Fixed in 2025.4.4
  3. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-core to a version that resolves this vulnerability.

    Fixed in 2026.0.3
  4. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-core to a version that resolves this vulnerability.

    Fixed in 2025.4.4
  5. Upgrade

    Upgrade maven/io.spinnaker.orca:orca-core to a version that resolves this vulnerability.

    Fixed in 2025.3.3
  6. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-core to a version that resolves this vulnerability.

    Fixed in 2025.3.3
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2026.1.0
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2026.0.3
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2025.4.4
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2025.3.3
  11. Compensating control

    Disable the CloudFormation system and cloudfoundry baking operations to avoid unsafe YAML processing bypass during CloudFormation deployments or CloudFoundry baking.

Event History

Jun 22, 2026
Advisory Published
via GitHub·08:43 PM
Data Sourced
via GitHub·08:43 PM
DescriptionSeverityWeaknessAffected Software
Jul 10, 2026
CVE Published
via MITRE·09:49 PM
Data Sourced
via MITRE·09:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44795?

The severity of CVE-2026-44795 is high, rated at 8.5.

2

What type of vulnerability is CVE-2026-44795?

CVE-2026-44795 is an unsafe YAML processing vulnerability that allows arbitrary loading of Java classes.

3

How does CVE-2026-44795 affect cloud services?

CVE-2026-44795 impacts users during CloudFormation deployments and CloudFoundry Baking.

4

What is the risk associated with CVE-2026-44795?

CVE-2026-44795 has a risk score of 55.

5

How do I mitigate CVE-2026-44795?

To mitigate CVE-2026-44795, users should apply the available patches and avoid using non-safe constructors.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203