dbcve.org
SpinnakerApplication · Linuxfoundation

CVE-2026-44795

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2025.3.3 / 2025.4.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3, unsafe YAML processing bypasses safe deserialization when using CloudFormation deployments or CloudFoundry baking. The use of a non-safe constructor allows arbitrary loading of Java classes, leading to remote code execution. This issue is fixed in versions 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spinnaker contains an unsafe YAML deserialization vulnerability in its CloudFormation deployment and CloudFoundry baking features. The YAML processing uses a non-safe constructor that bypasses safe deserialization protections, allowing arbitrary Java class loading and leading to remote code execution.

MitigationUpgrade Spinnaker to versions 2026.1.0, 2026.0.3, 2025.4.4, or 2025.3.3 or later to patch the unsafe YAML constructor. If immediate patching is not possible, restrict or disable CloudFormation deployments and CloudFoundry baking features until the upgrade can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SpinnakerApplication
Affected:< 2025.3.3>= 2025.4.0, < 2025.4.4>= 2026.0.0, < 2026.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spinnaker version
    Check the installed Spinnaker version via the halyard config or Kubernetes deployment manifests. Common locations: 'hal config version' command, or look for the Deck/Gate/Fiat service images/tags in your Kubernetes namespace.
    Affected if The installed version is < 2025.3.3, OR >= 2025.4.0 and < 2025.4.4, OR >= 2026.0.0 and < 2026.0.3
  2. Verify CloudFormation deployment feature is enabled
    Check Spinnaker configuration for CloudFormation provider enabled in 'hal config provider aws' or the clouddriver configuration. Look for 'cf' or 'cloudformation' in the enabled deployment strategies.
    Affected if CloudFormation deployment feature is enabled and the version is in any of the affected ranges listed above
  3. Verify CloudFoundry baking feature is enabled
    Examine the clouddriver or rosco service configuration for CloudFoundry bake support. Check for 'cloudfoundry' entries in the provider configuration or bake settings.
    Affected if CloudFoundry baking feature is enabled and the version is in any of the affected ranges listed above
  4. Confirm YAML processing is in use for these features
    Review the pipeline or task configuration that uses CloudFormation or CloudFoundry to confirm YAML input is processed. Check if custom templates or parameterized YAML files are loaded during deployment/baking.
    Affected if YAML files are processed by the CloudFormation or CloudFoundry features in a Spinnaker version within the affected ranges

You are affected if your Spinnaker version falls within the affected ranges AND either CloudFormation deployment or CloudFoundry baking features are enabled and process YAML input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.3.3 / 2025.4.4 / 2026.0.3 or later
Fixed in 2025.3.32025.4.42026.0.3
Vendor patch github.com →
Interim mitigation

Upgrade Spinnaker to versions 2026.1.0, 2026.0.3, 2025.4.4, or 2025.3.3 or later to patch the unsafe YAML constructor. If immediate patching is not possible, restrict or disable CloudFormation deployments and CloudFoundry baking features until the upgrade can be applied.

Recommended fix High confidence

Upgrade to Spinnaker 2026.1.0 (or 2026.0.3, 2025.4.4, or 2025.3.3)

  1. 1. Identify your current Spinnaker version by checking the deployment configuration or Spinnaker UI
  2. 2. Plan the upgrade to one of the fixed versions: 2026.1.0, 2026.0.3, 2025.4.4, or 2025.3.3
  3. 3. Back up your Spinnaker configuration and persistent data
  4. 4. Execute the upgrade following the official Spinnaker upgrade documentation for your deployment method
  5. 5. Verify the upgrade was successful by checking the Spinnaker version in the UI or via CLI
  6. 6. Test CloudFormation deployments and CloudFoundry baking functionality to confirm the vulnerability is remediated
Caveat Upgrading across major versions may introduce breaking changes; review release notes for your target version before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spinnaker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44795 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data