Skip to content
Fencer Intel
critical 9.9

CVE-2025-59823 json

Gardener providers vulnerable to code injection when Terraformer is used for infrastructure provisioning

published last yr. modified 29d ago also GHSA-227x-7mh8-3cf6 , GO-2025-3981 , EUVD-2025-31113

cvss
9.9
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

Project Gardener implements the automated management and operation of Kubernetes clusters as a service. Code injection may be possible in Gardener Extensions for AWS providers prior to version 1.64.0, Azure providers prior to version 1.55.0, OpenStack providers prior to version 1.49.0, and GCP providers prior to version 1.46.0. 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 affects all Gardener installations where Terraformer is used/can be enabled for infrastructure provisioning with any of the affected components. This issue has been patched in Gardener Extensions for AWS providers version 1.64.0, Azure providers version 1.55.0, OpenStack providers version 1.49.0, and GCP providers version 1.46.0.

Patch / fix

  • go github.com/gardener/gardener-extension-provider-aws 1.64.0
  • go github.com/gardener/gardener-extension-provider-gcp 1.46.0
  • go github.com/gardener/gardener-extension-provider-azure 1.55.0
  • go github.com/gardener/gardener-extension-provider-openstack 1.49.0
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251023T162509-150000.1.110.1

suse advisories SUSE-SU-2025:3799-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251023T162509-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15666-1

Is CVE-2025-59823 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 9.9 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.0 9.9 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/gardener/gardener-extension-provider-aws
<1.64.0
1.64.0
go github.com/gardener/gardener-extension-provider-gcp
<1.46.0
1.46.0
go github.com/gardener/gardener-extension-provider-azure
<1.55.0
1.55.0
go github.com/gardener/gardener-extension-provider-openstack
<1.49.0
1.49.0

Affected products

  • gardener gardener-extension-provider-aws

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.