Unsafe Deserialization in io.spinnaker.rosco:rosco-manifests (CVE-2026-55175)
Summary
Vulnerability in io.spinnaker.rosco:rosco-manifests (CVE-2026-55175). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2026.1.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55175 has been found in io.spinnaker.rosco:rosco-manifests.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade io.spinnaker.rosco:rosco-manifests to 2026.1.1 or later.
If unsure, ask your IT team or search "io.spinnaker.rosco:rosco-manifests CVE-2026-55175" on the vendor's site.
CVE-2026-55175 (io.spinnaker.rosco:rosco-manifests) — CWE-502 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in io.spinnaker.rosco:rosco-manifests.
Check the vendor advisory for the affected versions of io.spinnaker.rosco:rosco-manifests.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 2026.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.spinnaker.rosco:rosco-manifests を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.spinnaker.rosco:rosco-manifests to 2026.1.1ステージング環境で 2026.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com