GHSA-p68j-q7hf-3qcp: High severity maven/io.spinnaker.rosco:rosco-manifests vulnerability

Published Aug 28, 2026
·
Updated

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

Affected Software

4 affected componentsFixes available
maven/io.spinnaker.rosco:rosco-manifests>=2026.1.0<2026.1.1
2026.1.1
maven/io.spinnaker.rosco:rosco-manifests>=2026.0.0<2026.0.3
2026.0.3
maven/io.spinnaker.rosco:rosco-manifests>=2025.4.0<2025.4.4
2025.4.4
maven/io.spinnaker.rosco:rosco-manifests<2025.3.4
2025.3.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-manifests to a version that resolves this vulnerability.

    Fixed in 2026.1.1
  2. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-manifests to a version that resolves this vulnerability.

    Fixed in 2026.0.3
  3. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-manifests to a version that resolves this vulnerability.

    Fixed in 2025.4.4
  4. Upgrade

    Upgrade maven/io.spinnaker.rosco:rosco-manifests to a version that resolves this vulnerability.

    Fixed in 2025.3.4
  5. Configuration

    Disable kustomize bake operations and use another provider instead (this workaround is only possible when using Kustomize).

    Kustomize bakes kustomize bake operations = blocked/disabled

Event History

Aug 28, 2026
Advisory Published
via GitHub·06:35 PM
Data Sourced
via GitHub·06:35 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Exposure is limited to Rosco deployments that perform Kustomize bake operations. Deployments using other bake providers instead of Kustomize are not affected by this issue.

2

What does an attacker need to exploit the vulnerability?

An attacker needs the ability to trigger or influence a Kustomize bake operation with unsafe tag processing. The published vector also indicates network reachability, low privileges, and no user interaction requirement, although exploitation complexity is high.

3

What can be done if an update cannot be applied immediately?

Disable Kustomize bakes and use another provider. Blocking Kustomize operations prevents the affected unsafe tag-processing path from being used.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203