gardenctl is vulnerable to Command Injection when used with non‑POSIX shells

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

EPSS

• CVE-2025-67508: 0.24% estimated exploitation activity in the next 30 days; percentile 15.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

11 Dec 2025, 16:48 UTC

Last modified by the source

24 Mar 2026, 21:08 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fw33-qpx7-rhx2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-67508

Advisory: gardenctl is vulnerable to Command Injection when used with non‑POSIX shells
IDs: CVE-2025-67508, GHSA-fw33-qpx7-rhx2
Record: https://patchnext.com/advisories/cve-2025-67508 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gardener/gardenctl-v2 0.0.0-20251107111549-0bdc484cb5fb. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gardener/gardenctl-v2: affected < 0.0.0-20251107111549-0bdc484cb5fb; fixed in 0.0.0-20251107111549-0bdc484cb5fb

## Suggested inspection (read-only)
- Go github.com/gardener/gardenctl-v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gardener/gardenctl-v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fw33-qpx7-rhx2 (GitHub-reviewed advisory GHSA-fw33-qpx7-rhx2 lists affected ranges: Go github.com/gardener/gardenctl-v2 >=0 <0.0.0-20251107111549-0bdc484cb5fb)

Commands are suggestions: review each one before running it.