CVE-2025-47283
Gardener vulnerability
- Published19 May 2025
Description
Gardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 that could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster(s) where their shoot clusters are managed. This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters. `gardener/gardener` (`gardenlet`) is the affected component. Versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 fix the issue.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/gardener/gardener/commit/924b1575aae052bcda5a51fac8594d38fa3c41b0
- https://github.com/gardener/gardener/commit/b89cf2cd5067e82f364063d5241af73650a6e11d
- https://github.com/gardener/gardener/commit/bbd19b1dd3a31843d7b820172d37f75298dfaf8b
- https://github.com/gardener/gardener/commit/cf4e9887d83902216b85609caf563f7a9dd2de00
- https://github.com/gardener/gardener/security/advisories/GHSA-3hw7-qj9h-r835
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-47283 being actively exploited?
CVE-2025-47283 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.65%.
How severe is CVE-2025-47283?
CVE-2025-47283 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 0.65% probability of exploitation.
Which products are affected by CVE-2025-47283?
Affected products include Gardener.
How do I fix CVE-2025-47283?
Upgrade affected software to a fixed version, for example Gardener 1.117.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-47283 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.