Skip to content
Fencer Vulns
high 7.1

CVE-2025-58063 json

CoreDNS: DNS Cache Pinning via etcd Lease ID Confusion

published 2025-09-09 13 mo ago modified 2026-10-19 20 d ago also EUVD-2025-33973 , GHSA-93mf-426m-g6x9 , GO-2025-3942

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

CoreDNS is a DNS server that chains plugins. Starting in version 1.2.0 and prior to version 1.12.4, the CoreDNS etcd plugin contains a TTL confusion vulnerability where lease IDs are incorrectly used as TTL values, enabling DNS cache pinning attacks. This effectively creates a DoS condition for DNS resolution of affected services. The `TTL()` function in `plugin/etcd/etcd.go` incorrectly casts etcd lease IDs (64-bit integers) to uint32 and uses them as TTL values. Large lease IDs become very large TTLs when cast to uint32. This enables cache pinning attacks. Version 1.12.4 contains a fix for the issue.

Patch / fix

  • go github.com/coredns/coredns 1.12.4
  • coredns.io coredns 1.12.4
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250918T182144-150000.1.107.1

suse advisories SUSE-SU-2025:03289-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • coredns openSUSE Leap 16.0 1.14.0-bp160.1.1
  • coredns openSUSE Tumbleweed 1.12.4-2.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250917T170349-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:20099-1openSUSE-SU-2025:15561-1openSUSE-SU-2025:15564-1

  • coredns Azure Linux 3.0 1.11.4-10
  • coredns CBL-Mariner 2.0 1.11.1-22

azure linux advisories AZL-67097AZL-67101

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-58063 updated cvss 5.4

github.com/coredns/coredns: CoreDNS Lease ID Confusion

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/lighthouse-agent-rhel9, rhacm2/lighthouse-coredns-rhel8
    affected: workaround, no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 4 openshift4/ose-coredns-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/coredns/coredns/security/advisories/GHSA-93mf-426m-g6x9 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Affected packages

ecosystem package affected fixed in
go github.com/coredns/coredns
>=1.2.0, <1.12.4
1.12.4

Affected products

  • coredns coredns

Classification

Weakness
  • CWE-681 Incorrect Conversion between Numeric Types

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.