dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-59823

CRITICAL · 9.9 CVSS v3.0 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Project Gardener implements the automated management and operation of Kubernetes clusters as a service. Code injection may be possible in Gardener Extensions for AWS providers prior to version 1.64.0, Azure providers prior to version 1.55.0, OpenStack providers prior to version 1.49.0, and GCP providers prior to version 1.46.0. This vulnerability could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster where the shoot cluster is managed. This affects all Gardener installations where Terraformer is used/can be enabled for infrastructure provisioning with any of the affected components. This issue has been patched in Gardener Extensions for AWS providers version 1.64.0, Azure providers version 1.55.0, OpenStack providers version 1.49.0, and GCP providers version 1.46.0.

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

A code injection vulnerability in Gardener Extensions for AWS, Azure, OpenStack, and GCP providers allows users with administrative privileges for a Gardener project to inject code and obtain control over the seed cluster that manages the shoot cluster, by exploiting Terraformer infrastructure provisioning.

MitigationUpgrade Gardener Extensions to AWS >= 1.64.0, Azure >= 1.55.0, OpenStack >= 1.49.0, or GCP >= 1.46.0. If upgrades are not immediately possible, restrict administrative privileges and disable Terraformer where not required.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/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 deployed Gardener cloud provider extensions
    List all Gardener extensions in the gardener-extension namespace: kubectl get deployments -n gardener-extension | grep -E 'provider-alicloud|provider-aws|provider-azure|provider-gcp|provider-openstack'
    Affected if Any of AWS, Azure, OpenStack, or GCP provider extensions are deployed
  2. Check AWS extension version
    Run: kubectl get deployment gardener-extension-provider-aws -n gardener-extension -o jsonpath='{.spec.template.spec.containers[0].image}' and compare the image tag to version 1.64.0
    Affected if The installed version is earlier than 1.64.0
  3. Check Azure extension version
    Run: kubectl get deployment gardener-extension-provider-azure -n gardener-extension -o jsonpath='{.spec.template.spec.containers[0].image}' and compare the image tag to version 1.55.0
    Affected if The installed version is earlier than 1.55.0
  4. Check OpenStack extension version
    Run: kubectl get deployment gardener-extension-provider-openstack -n gardener-extension -o jsonpath='{.spec.template.spec.containers[0].image}' and compare the image tag to version 1.49.0
    Affected if The installed version is earlier than 1.49.0
  5. Check GCP extension version
    Run: kubectl get deployment gardener-extension-provider-gcp -n gardener-extension -o jsonpath='{.spec.template.spec.containers[0].image}' and compare the image tag to version 1.46.0
    Affected if The installed version is earlier than 1.46.0
  6. Verify if Terraformer is in use for infrastructure
    Check Shoot or Infrastructure resources for Terraformer configuration: kubectl get infrastructure -A -o jsonpath='{range .items[*]}{.metadata.name}{.metadata.namespace}{.spec.terraformer}{end}'
    Affected if Terraformer is enabled or referenced in the infrastructure configuration

You are affected if you have any AWS, Azure, OpenStack, or GCP Gardener extensions running below their respective fixed versions AND Terraformer infrastructure provisioning is enabled for your shoots.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gardener Extensions to AWS >= 1.64.0, Azure >= 1.55.0, OpenStack >= 1.49.0, or GCP >= 1.46.0. If upgrades are not immediately possible, restrict administrative privileges and disable Terraformer where not required.

Recommended fix High confidence

AWS: 1.64.0, Azure: 1.55.0, OpenStack: 1.49.0, GCP: 1.46.0

  1. Identify which Gardener Extension provider is in use (AWS, Azure, OpenStack, or GCP) by checking the Gardener installation
  2. Check the current version of the affected provider extension using 'kubectl get extension -n <project-namespace>' or via Gardener dashboard
  3. For AWS provider: Upgrade to version 1.64.0 or later
  4. For Azure provider: Upgrade to version 1.55.0 or later
  5. For OpenStack provider: Upgrade to version 1.49.0 or later
  6. For GCP provider: Upgrade to version 1.46.0 or later
  7. Verify the upgrade was successful and the extension is running the patched version
  8. Test that shoot cluster creation and management still functions correctly after the upgrade
Caveat Review Gardener extension release notes for any breaking changes between current and target version; test thoroughly in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59823 — 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-2025-59823 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