Skip to main content
VulnerabilityPublished Updated

CVE-2025-67508: gardener gardenctl-v2 · Command Injection

Affects gardener gardenctl-v2Source CVE Database V5

0

Not known to be exploited · CVSS 8.0 High : upgrade to 2.12.0 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.12.0
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade gardener/gardenctl-v2 to 2.12.0.

Affected software

ProductAffectedFixed in
GitHubgardener/gardenctl-v2pkg:github/gardener/gardenctl-v2Other threatsAffected
  • <2.12.0
Fixed in
  • 2.12.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade gardenctl-v2 to version 2.12.0 or later to apply the official fix that neutralizes special elements in credential values. In addition, organizations should audit and restrict administrative privileges within Gardener projects to minimize the risk of malicious credential injection. Implement strict credential validation and sanitization policies before storing secrets in infrastructure objects. Limit the use of non-POSIX shells such as Fish and PowerShell for evaluating sensitive credentials or consider enforcing POSIX-compliant shells where feasible. Monitor and log usage of gardenctl and related CLI tools, especially commands involving credential management, to detect anomalous activities. Conduct regular security training for operators to recognize and avoid executing untrusted or suspicious credential data. Employ multi-factor authentication and robust identity management to protect administrative accounts. Finally, implement network segmentation and least privilege principles to contain potential exploitation impact.

Description

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.

References

Community reviews

Loading reviews…