← Back
CVE-2026-44795
Vulnerability in io.spinnaker.rosco:rosco-core (CVE-2026-44795)
Summary
vulnerability in io.spinnaker.rosco:rosco-core (CVE-2026-44795). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2025.3.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44795** has been found in io.spinnaker.rosco:rosco-core.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade io.spinnaker.rosco:rosco-core to **2025.3.3** or later.
If unsure, ask your IT team or search "io.spinnaker.rosco:rosco-core CVE-2026-44795" on the vendor's site.
CVE-2026-44795 (io.spinnaker.rosco:rosco-core) — CWE-470 /
Patched: `2025.3.3` — apply immediately
Workaround: Disable the CloudFormation system and cloudfoundry baking operations.
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
**A vulnerability** (CWE-470) exists in io.spinnaker.rosco:rosco-core.
📍 Affected scope
io.spinnaker.rosco:rosco-core — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2025.3.3**.
🛡️ Workaround
Workaround: Disable the CloudFormation system and cloudfoundry baking operations.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.spinnaker.rosco:rosco-core' .` 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-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.spinnaker.rosco:rosco-core` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Disable the CloudFormation system and cloudfoundry baking operations.パッチが適用されるまでの応急処置として、Disable the CloudFormation system and cloudfoundry baking operations. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade io.spinnaker.rosco:rosco-core to 2025.3.3ステージング環境で 2025.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.spinnaker.rosco:rosco-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.0.3"}]}]
maven
io.spinnaker.orca:orca-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.0.3"}]}]