Advisory record · GHSA-c8q4-9h32-2ww8

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

CVSS 8.8 HighEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 22 Jun 2026, 20:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.spinnaker.rosco:rosco-coreMaven<2025.3.3 || >=2025.4.0, <2025.4.4 || >=2026.0.0, <2026.0.32025.3.3, 2025.4.4, 2026.0.3
io.spinnaker.orca:orca-coreMaven<2025.3.3 || >=2025.4.0, <2025.4.4 || >=2026.0.0, <2026.0.32025.3.3, 2025.4.4, 2026.0.3
Identifiers
GHSA-c8q4-9h32-2ww8 · CVE-2026-44795
Weakness (CWE)
CWE-470 · CWE-502
Published
22 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spinnaker's rosco-core and orca-core Maven packages are affected in versions before 2025.3.3, from 2025.4.0 before 2025.4.4, and from 2026.0.0 before 2026.0.3. Unsafe YAML processing during CloudFormation deployments and CloudFoundry baking allows arbitrary Java class loading, which can lead to remote code execution. Upgrade to 2025.3.3, 2025.4.4, or 2026.0.3, depending on your release line. Until then, the source suggests disabling the CloudFormation and CloudFoundry baking operations.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.