CVE-2025-67508 — gardenctl-v2
HIGHCVE-2025-67508 is a high-severity (CVSS 8) CWE-77 vulnerability in github.com/gardener/gardenctl-v2. A fix is available for github.com/gardener/gardenctl-v2 — see the affected versions and patch details below.
gardenctl is vulnerable to Command Injection when used with non‑POSIX shells
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67508.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/gardener/gardenctl-v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gardener/gardenctl-v2 | all versions | 0.0.0-20251107111549-0bdc484cb5fbgo get github.com/gardener/gardenctl-v2@v0.0.0-20251107111549-0bdc484cb5fb |
Affected Products
gardenctllinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gardener/gardenctl-v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gardener/gardenctl-v2 to 0.0.0-20251107111549-0bdc484cb5fb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67508 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2025-67508 in your dependencies?
Find it across Go, including transitive dependencies.