Skip to content

Spinnaker has uon-safe yaml deserialization, allowing RCE when using specific types

High severity GitHub Reviewed Published Jun 15, 2026 in spinnaker/spinnaker • Updated Jun 22, 2026

Package

maven io.spinnaker.orca:orca-core (Maven)

Affected versions

< 2025.3.3
>= 2025.4.0, < 2025.4.4
>= 2026.0.0, < 2026.0.3

Patched versions

2025.3.3
2025.4.4
2026.0.3
maven io.spinnaker.rosco:rosco-core (Maven)
< 2025.3.3
>= 2025.4.0, < 2025.4.4
>= 2026.0.0, < 2026.0.3
2025.3.3
2025.4.4
2026.0.3

Description

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!

References

@jasonmcintosh jasonmcintosh published to spinnaker/spinnaker Jun 15, 2026
Published to the GitHub Advisory Database Jun 22, 2026
Reviewed Jun 22, 2026
Last updated Jun 22, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

EPSS score

Weaknesses

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

The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code. Learn more on MITRE.

Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. Learn more on MITRE.

CVE ID

CVE-2026-44795

GHSA ID

GHSA-c8q4-9h32-2ww8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.