CVE-2026-32604: Linuxfoundation Spinnaker remote code execution (CVSS 9.9)

Description

Spinnaker is an open source, multi-cloud continuous delivery platform. In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, a bad actor can execute arbitrary commands very simply on the clouddriver pods. This can expose credentials, remove files, or inject resources easily. Versions 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2 contain a patch. As a workaround, disable the gitrepo artifact types.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Linuxfoundation Spinnaker≥ 2025.4.0 < 2025.4.2 · ≥ 2026.0.0 < 2026.0.1 · < 2025.3.2

Remediation

Fixed in

Linuxfoundation Spinnaker≥ 2025.4.2

Patch & vendor advisories

https://github.com/spinnaker/spinnaker/security/advisories/GHSA-x3j7-7pgj-h87r

References

https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2ProductRelease Notes
https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2ProductRelease Notes
https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1ProductRelease Notes
https://github.com/spinnaker/spinnaker/security/advisories/GHSA-x3j7-7pgj-h87rMitigationVendor Advisory
https://zeropath.com/blog/spinnaker-rce-production-compromise

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-32604 being actively exploited?

CVE-2026-32604 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.77%.

How severe is CVE-2026-32604?

CVE-2026-32604 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 0.77% probability of exploitation.

Which products are affected by CVE-2026-32604?

Affected products include Linuxfoundation Spinnaker.

How do I fix CVE-2026-32604?

Upgrade affected software to a fixed version, for example Linuxfoundation Spinnaker 2025.4.2 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-32604 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo