Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44795 high CVSS 8.8

Vulnerability in io.spinnaker.rosco:rosco-core (CVE-2026-44795)

Summary

Vulnerability in io.spinnaker.rosco:rosco-core (CVE-2026-44795). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2025.3.3 or later.

Original description

The description as published by the source.

Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3, unsafe YAML processing bypasses safe deserialization when using CloudFormation deployments or CloudFoundry baking. The use of a non-safe constructor allows arbitrary loading of Java classes, leading to remote code execution. This issue is fixed in versions 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3.

Source: GitHub Security Advisories (Global) 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-44795 has been found in io.spinnaker.rosco:rosco-core.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/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 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
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

Check the vendor advisory for the affected versions of io.spinnaker.rosco:rosco-core.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.spinnaker.rosco:rosco-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply temporary workaround mitigate 
    Disable the CloudFormation system and cloudfoundry baking operations.

    パッチが適用されるまでの応急処置として、Disable the CloudFormation system and cloudfoundry baking operations. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade io.spinnaker.rosco:rosco-core to 2025.3.3

    ステージング環境で 2025.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details