CVE-2026-44795

Spinnaker has uon-safe yaml deserialization, allowing RCE when using specific types

Workarounds

Disable the CloudFormation system and cloudfoundry baking operations.

Resources

Join Spinnaker on Slack for more information!

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.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2026-44795 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2025.3.3, 2025.4.4, 2026.0.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

2025.3.3, 2026.0.3 and 2025.4.4.

1. What is CVE-2026-44795? CVE-2026-44795 is a high-severity insecure deserialization vulnerability in io.spinnaker.rosco:rosco-core (maven), affecting versions < 2025.3.3. It is fixed in 2025.3.3, 2025.4.4, 2026.0.3. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2026-44795? CVE-2026-44795 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-44795?
   • io.spinnaker.rosco:rosco-core (maven) (versions < 2025.3.3)
   • io.spinnaker.orca:orca-core (maven) (versions < 2025.3.3)
4. Is there a fix for CVE-2026-44795? Yes. CVE-2026-44795 is fixed in 2025.3.3, 2025.4.4, 2026.0.3. Upgrade to this version or later.
5. Is CVE-2026-44795 exploitable, and should I be worried? Whether CVE-2026-44795 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44795 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44795?
   • Upgrade io.spinnaker.rosco:rosco-core to 2025.3.3 or later
   • Upgrade io.spinnaker.orca:orca-core to 2025.3.3 or later
   • Upgrade io.spinnaker.rosco:rosco-core to 2025.4.4 or later
   • Upgrade io.spinnaker.rosco:rosco-core to 2026.0.3 or later
   • Upgrade io.spinnaker.orca:orca-core to 2025.4.4 or later
   • Upgrade io.spinnaker.orca:orca-core to 2026.0.3 or later