CVE-2026-44795highCWE-470CWE-502

CVE-2026-44795: high-severity vulnerability in spinnaker

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

Published · Updated

Follow this CVE+ Monitor spinnaker+ Monitor io.spinnaker.orca:orca-core

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8.8epss 1.0%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
spinnaker · spinnaker
Related CVEs — spinnaker

In the same product, most dangerous first.

CVE-2021-43832CRITICALImproper Access Control in spinnakerEPSS 2.7%CVE-2026-55175HIGHSpinnaker: Improper yaml processing on kustomize bake operationsEPSS 1.1%CVE-2026-32604CRITICALSpinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and pathsEPSS 0.6%CVE-2022-23506MEDIUMSpinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer buildsEPSS 0.6%CVE-2026-32613CRITICALSpinnaker vulnerable to RCE via expression parsing due to unrestricted context handlingEPSS 0.6%CVE-2023-39348MEDIUMImproper log output when using GitHub Status Notifications in spinnakerEPSS 0.4%