Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-p68j-q7hf-3qcp

Spinnaker: Improper yaml processing on kustomize bake operations

CVSS 7.5 HighEPSS 0.011 · 64th percentile

Published by the GitHub Advisory Database at 28 Aug 2026, 18:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.spinnaker.rosco:rosco-manifestsMaven<2025.3.4 || >=2025.4.0, <2025.4.4 || >=2026.0.0, <2026.0.3 || >=2026.1.0, <2026.1.12025.3.4, 2025.4.4, 2026.0.3, 2026.1.1
Identifiers
GHSA-p68j-q7hf-3qcp · CVE-2026-55175
Weakness (CWE)
CWE-502
Tags
Published
28 Aug 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spinnaker's rosco-manifests Maven package (io.spinnaker.rosco:rosco-manifests) is affected in versions before 2025.3.4, from 2025.4.0 before 2025.4.4, from 2026.0.0 before 2026.0.3, and from 2026.1.0 before 2026.1.1. Unsafe YAML tag processing during kustomize bake operations can lead to remote code execution on rosco pods; the source does not say what access an attacker needs. To fix this, upgrade to 2025.3.4, 2025.4.4, 2026.0.3, or 2026.1.1. As a workaround, disable kustomize bakes or use another manifest provider.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.011, the 64th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.