CVE-2026-55175 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in io.spinnaker.rosco:rosco-manifests. A fix is available for io.spinnaker.rosco:rosco-manifests — see the affected versions and patch details below.
Spinnaker: Improper yaml processing on kustomize bake operations
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 CVE-2026-55175.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-55175 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
io.spinnaker.rosco:rosco-manifests☕io.spinnaker.rosco:rosco-manifests☕io.spinnaker.rosco:rosco-manifests☕io.spinnaker.rosco:rosco-manifestsReal-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
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.spinnaker.rosco:rosco-manifests | all versions | 2025.3.4io.spinnaker.rosco:rosco-manifests:2025.3.4 |
| ☕Maven | io.spinnaker.rosco:rosco-manifests | ≥ 2025.4.0&&< 2025.4.4 | 2025.4.4io.spinnaker.rosco:rosco-manifests:2025.4.4 |
| ☕Maven | io.spinnaker.rosco:rosco-manifests | ≥ 2026.0.0&&< 2026.0.3 | 2026.0.3io.spinnaker.rosco:rosco-manifests:2026.0.3 |
| ☕Maven | io.spinnaker.rosco:rosco-manifests | ≥ 2026.1.0&&< 2026.1.1 | 2026.1.1io.spinnaker.rosco:rosco-manifests:2026.1.1 |
Affected Products
spinnakerlinuxfoundationDetection & 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-manifests, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.spinnaker.rosco:rosco-manifests to 2025.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55175 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
Is CVE-2026-55175 in your dependencies?
Find it across Maven, including transitive dependencies.