CVE-2025-67508
HIGHCVE-2025-67508 is a high-severity (CVSS 8) CWE-77 vulnerability in github.com/gardener/gardenctl-v2. O3 Security confirms whether CVE-2025-67508 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
gardenctl is vulnerable to Command Injection when used with non‑POSIX shells
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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gardener/gardenctl-v2 | all versions | 0.0.0-20251107111549-0bdc484cb5fb |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-67508 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-67508. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-67508 in your dependencies?
O3 detects CVE-2025-67508 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.