Summary
Affected Components
• gardener-extension-provider-gcp
• gardener-extension-provider-azure
• gardener-extension-provider-openstack
• gardener-extension-provider-aws
Affected Versions
• gardener-extension-provider-gcp < v1.46.0
• gardener-extension-provider-azure < v1.55.0
• gardener-extension-provider-openstack < v1.49.0
• gardener-extension-provider-aws < v1.64.0
Fixed versions
• gardener-extension-provider-gcp >= v1.46.0
• gardener-extension-provider-azure >= v1.55.0
• gardener-extension-provider-openstack >= v1.49.0
• gardener-extension-provider-aws >= v1.64.0
How do I mitigate this vulnerability?
Update to a fixed version.
Impact
A security vulnerability was discovered in Gardener when Terraformer is used for infrastructure provisioning. This vulnerability could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster where the shoot cluster is managed.
This CVE affects all Gardener installations where Terraformer is used/can be enabled for infrastructure provisioning with any of the affected components mentioned below.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2025-59823 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. 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 (1.64.0, 1.46.0, 1.55.0, 1.49.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
github.com/gardener/gardener-extension-provider-aws to 1.64.0 or later; github.com/gardener/gardener-extension-provider-gcp to 1.46.0 or later; github.com/gardener/gardener-extension-provider-azure to 1.55.0 or later; github.com/gardener/gardener-extension-provider-openstack to 1.49.0 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-59823? CVE-2025-59823 is a critical-severity improper input validation vulnerability in github.com/gardener/gardener-extension-provider-aws (go), affecting versions < 1.64.0. It is fixed in 1.64.0, 1.46.0, 1.55.0, 1.49.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- How severe is CVE-2025-59823? CVE-2025-59823 has a CVSS score of 9.9 (Critical). 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.
- Which packages are affected by CVE-2025-59823?
github.com/gardener/gardener-extension-provider-aws(go) (versions < 1.64.0)github.com/gardener/gardener-extension-provider-gcp(go) (versions < 1.46.0)github.com/gardener/gardener-extension-provider-azure(go) (versions < 1.55.0)github.com/gardener/gardener-extension-provider-openstack(go) (versions < 1.49.0)
- Is there a fix for CVE-2025-59823? Yes. CVE-2025-59823 is fixed in 1.64.0, 1.46.0, 1.55.0, 1.49.0. Upgrade to this version or later.
- Is CVE-2025-59823 exploitable, and should I be worried? Whether CVE-2025-59823 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
- What actually determines whether CVE-2025-59823 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.
- How do I fix CVE-2025-59823?
- Upgrade
github.com/gardener/gardener-extension-provider-awsto 1.64.0 or later - Upgrade
github.com/gardener/gardener-extension-provider-gcpto 1.46.0 or later - Upgrade
github.com/gardener/gardener-extension-provider-azureto 1.55.0 or later - Upgrade
github.com/gardener/gardener-extension-provider-openstackto 1.49.0 or later
- Upgrade