What is the CVSS score of CVE-2026-44795?

CVE-2026-44795 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.0%.

Which versions of Spinnaker are affected by CVE-2026-44795?

Spinnaker deployment services face remote code execution risk from authenticated users with pipeline access, potentially compromising deployment infrastructure and all downstream applications.. A patch is available.

How to fix or mitigate CVE-2026-44795?

Within 24 hours: identify all Spinnaker Rosco and Orca instances in use, audit users with pipeline access and restrict to minimum necessary, implement monitoring for suspicious YAML patterns in pipeline definitions. Within 7 days: apply vendor-released patch available per vendor advisory to all affected Spinnaker service instances. Within 30 days: conduct full audit of pipeline access controls, enforce least-privilege access policies, and validate patch deployment across all environments.

Spinnaker CVE-2026-44795

HIGH

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') (CWE-470)

2026-06-22 https://github.com/spinnaker/spinnaker

GHSA-c8q4-9h32-2ww8

Java Deserialization

8.8

CVSS 3.1 · Vendor: https://github.com/spinnaker/spinnaker

Severity by source

Vendor (https://github.com/spinnaker/spinnaker) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.8 HIGH

Network-reachable service with low-complexity YAML injection, but requires an authenticated pipeline user (PR:L), yielding full host compromise (C/I/A:H) without scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/spinnaker/spinnaker).

CVSS VectorVendor: https://github.com/spinnaker/spinnaker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Jul 10, 2026 - 22:30 vuln.today

v3 (cvss_changed)

Analysis Updated

Jul 10, 2026 - 22:30 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jul 10, 2026 - 22:22 vuln.today

cvss_changed

CVSS changed

Jul 10, 2026 - 22:22 NVD

8.5 (HIGH) 8.8 (HIGH)

Re-analysis Queued

Jul 10, 2026 - 22:22 vuln.today

cvss_changed

CVSS changed

Jul 10, 2026 - 22:22 NVD

8.5 (HIGH) 8.8 (HIGH)

Source Code Evidence Fetched

Jun 22, 2026 - 21:20 vuln.today

Analysis Generated

Jun 22, 2026 - 21:20 vuln.today

DescriptionCVE.org

Impact

There's an unsafe YAML processing vulnerability that bypasses safe deserialization. This impacts users when when performing:

CloudFormation deployments
CloudFoundry Baking

The usage of a non-safe constructor use allows arbitrary loading of Java classes leading to RCE.

Patches

2025.3.3, 2026.0.3 and 2025.4.4.

Workarounds

Disable the CloudFormation system and cloudfoundry baking operations.

Resources

Join Spinnaker on Slack for more information!

AnalysisAI

Remote code execution in Spinnaker's Rosco and Orca services arises because YAML input is parsed with SnakeYAML's unsafe default Constructor rather than a SafeConstructor, letting authenticated users who trigger CloudFormation deployments or CloudFoundry baking load arbitrary Java classes. An attacker with pipeline access can supply a crafted YAML tag (e.g. !!javax.script.ScriptEngineManager) to instantiate dangerous classes and reach code execution on the affected service host. No public weaponized exploit is identified, though the vendor fix commit ships tests demonstrating the arbitrary-object-instantiation primitive, and the flaw is not listed in CISA KEV.

Technical ContextAI

Spinnaker is a multi-cloud continuous-delivery platform; the affected components are the Rosco (rosco-core) image-baking service and the Orca (orca-core) orchestration engine, both Java/Kotlin Maven artifacts. The root cause is CWE-470 (unsafe reflection / use of externally-controlled input to select classes) realized through SnakeYAML: the shared YamlHelper.newYaml() helper returns a parser built on the standard Constructor, which honors explicit YAML type tags such as !!java.net.URL or !!javax.script.ScriptEngineManager and reflectively instantiates those classes. This is the same vulnerability class as CVE-2022-1471 (SnakeYAML SafeConstructor bypass). The fix commit (4cbe1d5) routes deserialization through a new newYamlSafeConstructor() that rejects arbitrary class tags with a ConstructorException, and adds a deprecation warning to newYaml() flagging it as unsafe for untrusted input.

RemediationAI

Vendor-released patch: upgrade Spinnaker to 2025.3.3, 2025.4.4, or 2026.0.3 depending on your release train (these route YAML parsing through the new SafeConstructor). If immediate patching is not possible, apply the vendor workaround by disabling the CloudFormation deployment system and CloudFoundry baking operations, which removes the vulnerable input paths at the cost of losing those deployment/baking capabilities. As an additional compensating control, restrict who can author and trigger pipelines and treat pipeline definitions from untrusted or multi-tenant sources as hostile, since exploitation requires the ability to submit YAML into those flows. Track the fix via commits 4cbe1d5fea9df573aadfd8b093fb4b594b354ee5, e57c0db4584b398473a7bbb19402ce6c1e89b627, and f69d7b534d068ed74d0d3a1fbf17e2c945d36e5e, and the advisory at https://github.com/spinnaker/spinnaker/security/advisories/GHSA-c8q4-9h32-2ww8.