How severe is GHSA-c8q4-9h32-2ww8?

GHSA-c8q4-9h32-2ww8 has a CVSS score of 8.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-c8q4-9h32-2ww8?

GHSA-c8q4-9h32-2ww8 affects the following packages: io.spinnaker.rosco:rosco-core (Maven), io.spinnaker.orca:orca-core (Maven), io.spinnaker.rosco:rosco-core (Maven), io.spinnaker.rosco:rosco-core (Maven), io.spinnaker.orca:orca-core (Maven), io.spinnaker.orca:orca-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-c8q4-9h32-2ww8?

Update io.spinnaker.rosco:rosco-core to 2025.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8q4-9h32-2ww8 is resolved across your whole dependency graph.

How do I detect GHSA-c8q4-9h32-2ww8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spinnaker.rosco:rosco-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c8q4-9h32-2ww8 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-c8q4-9h32-2ww8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c8q4-9h32-2ww8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c8q4-9h32-2ww8?

GHSA-c8q4-9h32-2ww8 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c8q4-9h32-2ww8?

GHSA-c8q4-9h32-2ww8 is classified as CWE-470 (CWE-470), Deserialization of Untrusted Data (CWE-502). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c8q4-9h32-2ww8 published, and has it been updated?

GHSA-c8q4-9h32-2ww8 was published on June 22, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Spinnaker has non-safe yaml deserialization, allowing RCE when using specific typesGHSA-c8q4-9h32-2ww8

HIGHFix: spinnaker/spinnaker@4cbe1d5

GHSA-c8q4-9h32-2ww8 is a high-severity (CVSS 8.5) CWE-470 vulnerability in io.spinnaker.rosco:rosco-core. A fix is available for io.spinnaker.rosco:rosco-core — see the affected versions and patch details below.

Also known asCVE-2026-44795

Published

Jun 22, 2026

Updated

Sep 10, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c8q4-9h32-2ww8.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-c8q4-9h32-2ww8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

☕io.spinnaker.rosco:rosco-core☕io.spinnaker.orca:orca-core☕io.spinnaker.rosco:rosco-core☕io.spinnaker.rosco:rosco-core☕io.spinnaker.orca:orca-core☕io.spinnaker.orca:orca-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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!

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.spinnaker.rosco:rosco-core`	all versions	2025.3.3`io.spinnaker.rosco:rosco-core:2025.3.3`
☕Maven	`io.spinnaker.orca:orca-core`	all versions	2025.3.3`io.spinnaker.orca:orca-core:2025.3.3`
☕Maven	`io.spinnaker.rosco:rosco-core`	≥ 2025.4.0&&< 2025.4.4	2025.4.4`io.spinnaker.rosco:rosco-core:2025.4.4`
☕Maven	`io.spinnaker.rosco:rosco-core`	≥ 2026.0.0&&< 2026.0.3	2026.0.3`io.spinnaker.rosco:rosco-core:2026.0.3`
☕Maven	`io.spinnaker.orca:orca-core`	≥ 2025.4.0&&< 2025.4.4	2025.4.4`io.spinnaker.orca:orca-core:2025.4.4`
☕Maven	`io.spinnaker.orca:orca-core`	≥ 2026.0.0&&< 2026.0.3	2026.0.3`io.spinnaker.orca:orca-core:2026.0.3`

Affected Products

1 product · 3 configurations

Application

spinnakerlinuxfoundation

≥ 2026.0.0 && < 2026.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spinnaker.rosco:rosco-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.spinnaker.rosco:rosco-core to 2025.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8q4-9h32-2ww8 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

### 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!