dbcve.org
GardenctlApplication · Linuxfoundation

CVE-2025-67508

HIGH · 8.4 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 2.12.0 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable

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
gardenctl is a command-line client for the Gardener which configures access to clusters and cloud provider CLI tools. When using non‑POSIX shells such as Fish and PowerShell, versions 2.11.0 and below of gardenctl allow an attacker with administrative privileges for a Gardener project to craft malicious credential values. The forged credential values are used in infrastructure Secret objects that break out of the intended string context when evaluated in Fish or PowerShell environments used by the Gardener service operators. This issue is fixed in version 2.12.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

gardenctl versions 2.11.0 and below contain an injection vulnerability affecting non-POSIX shells (Fish/PowerShell). An attacker with Gardener project administrative privileges can craft malicious credential values in infrastructure Secret objects that break out of string context when evaluated by operator shell environments, potentially allowing command injection.

MitigationUpgrade gardenctl to version 2.12.0 or later. Review and rotate any credentials that may have been created or modified by users with administrative project privileges since the vulnerability was present.

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
GardenctlApplication
Affected:< 2.12.0

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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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. Check gardenctl version
    Run 'gardenctl version' or 'gardenctl --version' to determine the installed version
    Affected if Version is 2.11.0 or below (versions prior to 2.12.0)
  2. Identify shell environment
    Check which shell is active: echo $SHELL, or for Fish run 'echo $version', for PowerShell run '$PSVersionTable.PSVersion'
    Affected if Using Fish or PowerShell (non-POSIX shells) - POSIX shells (bash, zsh) are not affected by this specific vulnerability
  3. Verify Gardener administrative access
    Run 'gardenctl target control-plane' and list projects with 'gardenctl ls' to check if you have administrative project privileges
    Affected if User has Gardener project administrative privileges - this is required for the attack vector
  4. Inspect infrastructure Secret objects
    Use kubectl to list and examine Secret objects in Gardener project namespaces: 'kubectl get secrets -A' and review Secret data in infrastructure-related namespaces
    Affected if Infrastructure Secret objects contain credential values with special characters that could break string context in non-POSIX shells

You are affected if gardenctl version is below 2.12.0 AND you use Fish or PowerShell AND have Gardener project admin privileges with infrastructure Secrets that may contain maliciously crafted credential values.

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 2.12.0 or later
Fixed in 2.12.0
Interim mitigation

Upgrade gardenctl to version 2.12.0 or later. Review and rotate any credentials that may have been created or modified by users with administrative project privileges since the vulnerability was present.

Recommended fix High confidence

2.12.0

  1. 1. Check the current gardenctl version by running: gardenctl version
  2. 2. Download gardenctl version 2.12.0 or later from the official GitHub releases repository (github.com/gardener/gardenctl)
  3. 3. Install the new version following the platform-specific installation instructions
  4. 4. Verify the upgrade was successful by running: gardenctl version

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

Fix this in Gardenctl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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