CVE-2025-47283: Gardener implements the automated management and operation of Kubernetes clusters as a service

This month

CRITICAL 9.9WATCHLISTUPGRADE

CVE-2025-47283 is a critical-severity flaw (CVSS 9.9) affecting gardener. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 48%)
CISA exploited list	No
Weakness	CWE-20
Published	2025-05-19
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: gardener

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-19 19:15 UTCPublished CVE record published
2026-06-17 09:27 UTCUpdated Record last modified

gardener gardener UPGRADE

Affected: < 1.116.4 · >= 1.117.0 and < 1.117.5 · >= 1.118.0 and < 1.118.2

Fixed in: 1.116.4, 1.117.5, 1.118.2

Safe to downgrade to: a release before 1.117.0

1. Check installed version

apt-cache policy gardener || rpm -q gardener || gardener --version

2. UPGRADE to 1.116.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gardener

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gardener

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.117.0 (Debian / Ubuntu)

apt-cache madison gardener sudo apt install gardener=<VERSION_BEFORE_1.117.0> sudo apt-mark hold gardener

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gardener sudo dnf downgrade gardener-<VERSION_BEFORE_1.117.0> sudo dnf versionlock add gardener

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-47283?

gardener: upgrade to 1.116.4, 1.117.5, 1.118.2. Exact commands for each OS are on this page.

Is CVE-2025-47283 being exploited?

CVE-2025-47283 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-47283 affect?

CVE-2025-47283 affects gardener. Severity is critical (CVSS 9.9). 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 admini

How urgent is CVE-2025-47283?

Priority 53/100. Critical severity; On your watchlist

Software pages

Kubernetes vulnerabilities

Related CVEs

CVE-2025-47284 CRITICAL 9.9 UPGRADE Gardener implements the automated management and operation of Kubernetes clusters as a service

References

← Back to latest CVEs