CVE-2025-67508

A security vulnerability was discovered in gardenctl when it is used with non‑POSIX shells such as Fish and PowerShell. Such setup could allow an attacker with administrative privileges for a Gardener project to craft malicious credential values 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, leading to arbitrary command execution on the operator's device.

Am I vulnerable?
This CVE affects all Gardener operators who use gardenctl < v2.12.0 with non‑POSIX shells such as Fish and PowerShell.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2025-67508 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20251107111549-0bdc484cb5fb); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-67508? CVE-2025-67508 is a high-severity command injection vulnerability in github.com/gardener/gardenctl-v2 (go), affecting versions < 0.0.0-20251107111549-0bdc484cb5fb. It is fixed in 0.0.0-20251107111549-0bdc484cb5fb. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. How severe is CVE-2025-67508? CVE-2025-67508 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/gardener/gardenctl-v2 are affected by CVE-2025-67508? github.com/gardener/gardenctl-v2 (go) versions < 0.0.0-20251107111549-0bdc484cb5fb is affected.
4. Is there a fix for CVE-2025-67508? Yes. CVE-2025-67508 is fixed in 0.0.0-20251107111549-0bdc484cb5fb. Upgrade to this version or later.
5. Is CVE-2025-67508 exploitable, and should I be worried? Whether CVE-2025-67508 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-67508 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-67508? Upgrade github.com/gardener/gardenctl-v2 to 0.0.0-20251107111549-0bdc484cb5fb or later.