← Back
CVE-2026-55175
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in io.spinnaker.rosco:rosco-manifests.
📍 Affected scope
io.spinnaker.rosco:rosco-manifests — .
🔥 Severity
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2026.1.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.spinnaker.rosco:rosco-manifests' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'io.spinnaker.rosco:rosco-manifests' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.spinnaker.rosco:rosco-manifests` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.spinnaker.rosco:rosco-manifests to 2026.1.1ステージング環境で 2026.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.spinnaker.rosco:rosco-manifests
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.1.1"}]}]
References
- web https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- web https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- web https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- web https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- web https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- web https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- web https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- web https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- web https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- web https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- web https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
- web https://nvd.nist.gov/vuln/detail/CVE-2026-55175
- web https://github.com/advisories/GHSA-p68j-q7hf-3qcp