GHSA-c8q4-9h32-2ww8 is a high-severity (CVSS 8.5) CWE-470 vulnerability in io.spinnaker.rosco:rosco-core. O3 Security confirms whether GHSA-c8q4-9h32-2ww8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spinnaker has non-safe yaml deserialization, allowing RCE when using specific types
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-c8q4-9h32-2ww8 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 363,908 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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-coreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.spinnaker.rosco:rosco-core | all versions | 2025.3.3 |
| ☕Maven | io.spinnaker.orca:orca-core | all versions | 2025.3.3 |
| ☕Maven | io.spinnaker.rosco:rosco-core | ≥ 2025.4.0&&< 2025.4.4 | 2025.4.4 |
| ☕Maven | io.spinnaker.rosco:rosco-core | ≥ 2026.0.0&&< 2026.0.3 | 2026.0.3 |
| ☕Maven | io.spinnaker.orca:orca-core | ≥ 2025.4.0&&< 2025.4.4 | 2025.4.4 |
| ☕Maven | io.spinnaker.orca:orca-core | ≥ 2026.0.0&&< 2026.0.3 | 2026.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spinnaker.rosco:rosco-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c8q4-9h32-2ww8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c8q4-9h32-2ww8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-c8q4-9h32-2ww8 in your dependencies?
O3 detects GHSA-c8q4-9h32-2ww8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.