CVE-2025-47284
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in the `gardenlet` component of Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0. It 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 where gardener/gardener-extension-provider-gcp is in use. Versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 fix the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA privilege escalation vulnerability in Gardener's gardenlet component allows project administrators to gain unauthorized control over seed clusters hosting their shoot clusters. This affects only installations using the GCP provider extension (gardener/gardener-extension-provider-gcp).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.116.4>= 1.117.0, < 1.117.5>= 1.118.0, < 1.118.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify gardenlet versionRetrieve the version of the gardenlet component running in your Gardener installation. This is typically found in the gardenlet deployment or pod in the seed cluster, often viewable via kubectl get deployment -n garden gardenlet or by checking the container image tag.Affected if The installed version is less than 1.116.4, OR between 1.117.0 and 1.117.4 inclusive, OR between 1.118.0 and 1.118.1 inclusive.
-
Confirm GCP extension is deployedCheck if the gardener-extension-provider-gcp extension is installed in your Gardener environment. This can be done by listing extensions in the relevant namespaces or checking for the presence of the Extension resources with spec.type: provider-gcp.Affected if The gardener-extension-provider-gcp extension is present in your Gardener installation.
-
Check for GCP shoot clustersIdentify if you have any shoot clusters using the GCP provider. List shoot resources and filter by spec.provider.type: gcp or inspect your Gardener project for shoots with the GCP infrastructure type.Affected if Any shoot clusters in your Gardener project are using the GCP provider.
-
Verify project admin accessReview user permissions in your Gardener project to determine if any user has administrative privileges over the project, which would be required to exploit this vulnerability.Affected if Users with administrative privileges for the Gardener project exist and can manage shoots.
You are affected if gardenlet is running a version matching the affected ranges AND the GCP provider extension is deployed in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.116.41.117.51.118.2
Upgrade Gardener to version 1.116.4, 1.117.5, 1.118.2, or 1.119.0 to remediate. For unpatched installations, audit project admin permissions and monitor for unauthorized seed cluster access attempts.
Gardener 1.116.4, 1.117.5, 1.118.2, or 1.119.0 (latest: 1.119.0 recommended)
- 1. Identify the current Gardener version in use by checking the gardenlet deployment or the Gardener release notes
- 2. For Gardener versions < 1.116.4, upgrade to version 1.116.4 or later (preferably 1.119.0)
- 3. For Gardener versions 1.117.x where x < 5, upgrade to version 1.117.5 or later (preferably 1.119.0)
- 4. For Gardener versions 1.118.x where x < 2, upgrade to version 1.118.2 or later (preferably 1.119.0)
- 5. If using gardener/gardender-extension-provider-gcp, ensure it is also updated to be compatible with the chosen Gardener version
- 6. Test the upgrade in a staging environment before deploying to production
- 7. Apply the upgrade following Gardener's standard upgrade procedures documented at docs.gardener.cloud
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47284 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data