Skip to content

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

High severity GitHub Reviewed Published Dec 11, 2025 in gardener/gardenctl-v2 • Updated Dec 12, 2025

Package

gomod github.com/gardener/gardenctl-v2 (Go)

Affected versions

< 0.0.0-20251107111549-0bdc484cb5fb

Patched versions

0.0.0-20251107111549-0bdc484cb5fb

Description

A security vulnerability was discovered for 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.

References

@petersutter petersutter published to gardener/gardenctl-v2 Dec 11, 2025
Published to the GitHub Advisory Database Dec 11, 2025
Reviewed Dec 11, 2025
Published by the National Vulnerability Database Dec 12, 2025
Last updated Dec 12, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(14th percentile)

Weaknesses

Improper Neutralization of Special Elements used in a Command ('Command Injection')

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2025-67508

GHSA ID

GHSA-fw33-qpx7-rhx2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.