dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-47282

CRITICAL · 9.9 CVSS v3.0 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Gardener External DNS Management is an environment to manage external DNS entries for a kubernetes cluster. A security vulnerability was discovered in Gardener's External DNS Management prior to version 0.23.6 that could allow a user with administrative privileges for a Gardener project or a user with administrative privileges for a shoot cluster, including administrative privileges for a single namespace of the shoot cluster, to obtain control over the seed cluster where the shoot cluster is managed. This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters. The affected component is `gardener/external-dns-management`. The `external-dns-management` component may also be deployed on the seeds by the `gardener/gardener-extension-shoot-dns-service` extension when the extension is enabled. In this case, all versions of the `shoot-dns-service` extension `<= v1.60.0` are affected by this vulnerability. Version 0.23.6 of Gardener External DNS Management fixes 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 confidence

A privilege escalation vulnerability in Gardener External DNS Management allows users with administrative privileges on a Gardener project or shoot cluster (including a single namespace) to gain control over the seed cluster where the shoot cluster is managed. This is a critical cluster takeover issue affecting the external-dns-management component and the shoot-dns-service extension.

MitigationUpgrade gardener/external-dns-management to version 0.23.6 or later, and upgrade gardener-extension-shoot-dns-service to version v1.60.0 or later if deployed on seeds.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check external-dns-management deployment
    List all pods or deployments in the cluster that contain 'external-dns-management' in their name or labels, and retrieve their version information from image tags or chart versions
    Affected if The deployment exists and its version is below 0.23.6
  2. Check gardener-extension-shoot-dns-service version
    Identify if the shoot-dns-service extension is deployed on the seed cluster by querying for extensions with name 'shoot-dns-service' or related resources, then check its version from the deployment or custom resource definition
    Affected if The extension is deployed on the seed and its version is below v1.60.0
  3. Verify external-dns-management is enabled
    Inspect the Gardener Shoot cluster specification or the seed cluster's extension configurations to confirm that the external-dns-management component is actively enabled for the shoot
    Affected if The component is enabled and running a vulnerable version (below 0.23.6)
  4. Confirm user privilege scope
    Review the Gardener project membership and shoot cluster RBAC permissions to determine if any user has administrative privileges on a specific shoot namespace that could be exploited
    Affected if Users with admin-level access on individual shoot namespaces exist in the environment

A user is affected if the external-dns-management component is deployed at a version below 0.23.6, or the shoot-dns-service extension on seeds is below v1.60.0, and users with administrative privileges on shoot clusters or individual namespaces are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade gardener/external-dns-management to version 0.23.6 or later, and upgrade gardener-extension-shoot-dns-service to version v1.60.0 or later if deployed on seeds.

Recommended fix High confidence

Gardener External DNS Management version 0.23.6 or later; gardener-extension-shoot-dns-service v1.60.1 or later

  1. Identify all deployments of the external-dns-management component in your Gardener environment
  2. Identify if the gardener-extension-shoot-dns-service extension is deployed on any seeds; if so, note all affected extension versions (<= v1.60.0)
  3. Upgrade Gardener External DNS Management to version 0.23.6 or later
  4. If the shoot-dns-service extension is deployed, upgrade it to version v1.60.1 or later
  5. Verify the upgraded versions are running by checking the component versions in your deployments
  6. Review access controls and audit logs for any suspicious activity that may have occurred prior to patching

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47282 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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