CVE-2026-447958.8HighCWE-470

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

spinnaker

Affected: spinnaker · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.0%probability of exploitation in the next 30 days

63rd percentile

050100

Higher than 63% of scored CVEs

8.8HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

spinnaker · spinnaker>= 2025.4.0, < 2025.4.4; >= 2026.0.0, < 2026.0.3; < 2025.3.3

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of Externally-Controlled Input to Select Classes or Code · Command and Code Injection
Vendor: spinnaker
Published: July 2026
Band: Possible (1 to 10%), July 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-44795 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.