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.
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!
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.
maven
io.spinnaker.rosco:rosco-core (< 2025.3.3)io.spinnaker.orca:orca-core (< 2025.3.3)io.spinnaker.rosco:rosco-core (>= 2025.4.0, < 2025.4.4)io.spinnaker.rosco:rosco-core (>= 2026.0.0, < 2026.0.3)io.spinnaker.orca:orca-core (>= 2025.4.0, < 2025.4.4)io.spinnaker.orca:orca-core (>= 2026.0.0, < 2026.0.3)io.spinnaker.rosco:rosco-core → 2025.3.3 (maven)io.spinnaker.orca:orca-core → 2025.3.3 (maven)io.spinnaker.rosco:rosco-core → 2025.4.4 (maven)io.spinnaker.rosco:rosco-core → 2026.0.3 (maven)io.spinnaker.orca:orca-core → 2025.4.4 (maven)io.spinnaker.orca:orca-core → 2026.0.3 (maven)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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 instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2026-44795 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2026-44795 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-44795 in your environment →Upgrade the following packages to resolve this vulnerability:
io.spinnaker.rosco:rosco-core to 2025.3.3 or laterio.spinnaker.orca:orca-core to 2025.3.3 or laterio.spinnaker.rosco:rosco-core to 2025.4.4 or laterio.spinnaker.rosco:rosco-core to 2026.0.3 or laterio.spinnaker.orca:orca-core to 2025.4.4 or laterio.spinnaker.orca:orca-core to 2026.0.3 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
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.
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.
io.spinnaker.rosco:rosco-core (maven) (versions < 2025.3.3)io.spinnaker.orca:orca-core (maven) (versions < 2025.3.3)Yes. CVE-2026-44795 is fixed in 2025.3.3, 2025.4.4, 2026.0.3. Upgrade to this version or later.
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
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.
io.spinnaker.rosco:rosco-core to 2025.3.3 or laterio.spinnaker.orca:orca-core to 2025.3.3 or laterio.spinnaker.rosco:rosco-core to 2025.4.4 or laterio.spinnaker.rosco:rosco-core to 2026.0.3 or laterio.spinnaker.orca:orca-core to 2025.4.4 or laterio.spinnaker.orca:orca-core to 2026.0.3 or later