Skip to content

← Actionable
Critical, CVSS 9.9

Gardener External DNS Management allows malicious google credential in DNS secret to lead to privilege escalation

CVE-2025-47282GHSA-xwgg-m7fx-83wx

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/gardener/external-dns-management

    Affected
    < 0.23.6
    Fixed in
    0.23.6
  • Go github.com/gardener/gardener-extension-shoot-dns-service

    Affected
    <= 1.6.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2025-47282: 0.74% estimated exploitation activity in the next 30 days; percentile 54.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A security vulnerability was discovered in Gardener 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. Am I Vulnerable? This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters. Affected Components - gardener/external-dns-management Affected Versions - < 0.23.6 Fixed Versions - &gt;= 0.23.6 Important The external-dns-management component may also be deployed on the seeds by the https://github.com/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. How do I mitigate this vulnerability? Update to a fixed version.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xwgg-m7fx-83wx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-47282

Advisory: Gardener External DNS Management allows malicious google credential in DNS secret to lead to privilege escalation
IDs: CVE-2025-47282, GHSA-xwgg-m7fx-83wx
Record: https://patchnext.com/advisories/cve-2025-47282 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/gardener/external-dns-management 0.23.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gardener/external-dns-management: affected < 0.23.6; fixed in 0.23.6
- Go github.com/gardener/gardener-extension-shoot-dns-service: affected <= 1.6.0

## Suggested inspection (read-only)
- Go github.com/gardener/external-dns-management: check the installed version with your package manager.
- Go github.com/gardener/gardener-extension-shoot-dns-service: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gardener/external-dns-management, github.com/gardener/gardener-extension-shoot-dns-service.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xwgg-m7fx-83wx (GitHub-reviewed advisory GHSA-xwgg-m7fx-83wx lists affected ranges: Go github.com/gardener/external-dns-management >=0 =0 <=1.6.0)

Commands are suggestions: review each one before running it.

Loading voting…