Skip to content
Fencer Vulns
high 8.8

CVE-2026-44795 json

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

published 2026-06-22 4 mo ago modified 2026-09-10 1 mo ago also EUVD-2026-43086 , GHSA-c8q4-9h32-2ww8

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.spinnaker.rosco:rosco-core 2025.3.3, 2025.4.4, 2026.0.3
  • maven io.spinnaker.orca:orca-core 2025.3.3, 2025.4.4, 2026.0.3
  • io.spinnaker.orca orca-core 2025.3.3, 2025.4.4, 2026.0.3
  • linuxfoundation spinnaker 2025.3.3, 2025.4.4, 2026.0.3
  • io.spinnaker.rosco rosco-core 2025.3.3, 2025.4.4, 2026.0.3

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
3 mo ago

Exploit prediction

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven io.spinnaker.rosco:rosco-core
<2025.3.3
>=2025.4.0, <2025.4.4
>=2026.0.0, <2026.0.3
2025.3.3
2025.4.4
2026.0.3
maven io.spinnaker.orca:orca-core
<2025.3.3
>=2025.4.0, <2025.4.4
>=2026.0.0, <2026.0.3
2025.3.3
2025.4.4
2026.0.3

Affected products

  • spinnaker spinnaker

Classification

Weakness
  • CWE-470 Use of Externally-Controlled Input to Select Classes or Code
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.