Skip to content

Spinnaker: Improper yaml processing on kustomize bake operations

High severity GitHub Reviewed Published Jul 6, 2026 in spinnaker/spinnaker • Updated Aug 28, 2026

Package

maven io.spinnaker.rosco:rosco-manifests (Maven)

Affected versions

< 2025.3.4
>= 2025.4.0, < 2025.4.4
>= 2026.0.0, < 2026.0.3
>= 2026.1.0, < 2026.1.1

Patched versions

2025.3.4
2025.4.4
2026.0.3
2026.1.1

Description

Impact

Kustomize bake operations allow unsafe tag processing. This can lead to RCE type exploits on the rosco pods when doing kustomize bakes. This ONLY is possible when using Kustomize. The simple solution is to block kustomize operations and instead use another provider.

Workarounds

Disable kustomize bakes

References

@jasonmcintosh jasonmcintosh published to spinnaker/spinnaker Jul 6, 2026
Published by the National Vulnerability Database Jul 10, 2026
Published to the GitHub Advisory Database Aug 28, 2026
Reviewed Aug 28, 2026
Last updated Aug 28, 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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(64th percentile)

Weaknesses

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-55175

GHSA ID

GHSA-p68j-q7hf-3qcp

Source code

Credits

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