CVE-2026-26018

CoreDNS Loop Detection Denial of Service Vulnerability

Published Mar 6, 2026 CVSS 3.1 · 7.5 High EPSS 1.2% KEV · Not listed
Description
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.

Analysis

AI-generated

Technical impact

The flaw resides in CoreDNS’s loop detection plugin. An attacker can craft DNS queries that exploit the predictable pseudo‑random number generator used to generate secret query names, causing the plugin to raise a fatal error that terminates the entire DNS server. The outcome is a denial of service that can disrupt all clients relying on that DNS service. The weakness encompasses predictable PRNG use (CWE‑337), uncontrolled resource exhaustion (CWE‑400), and other related vulnerabilities (CWE‑1241, CWE‑770).

Affected Systems

CoreDNS, the DNS server software chain used by many container and cloud deployments. Versions earlier than 1.14.2 are affected; the vulnerability was fixed in the 1.14.2 release.

Risk and Exploitability

With a CVSS score of 7.5 the vulnerability is considered high severity. The EPSS score is below 1 %, indicating a low probability of current exploitation, and it has not appeared in the CISA Known Exploited Vulnerabilities catalog. The attack vector is inferred to be remote over the network, since an attacker only needs to send a specially crafted DNS query. A single successful request can crash the entire server, making rapid mitigation essential to preserve DNS availability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade CoreDNS to version 1.14.2 or later.
  • Configure rate‑limiting on DNS queries to lessen the impact of any future exploitation attempts.
  • Set up monitoring of DNS logs to detect abnormal query patterns that may indicate probing for this fault.

Generated by OpenCVE AI on April 16, 2026 at 11:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-h75p-j8xm-m278 CoreDNS Loop Detection Denial of Service Vulnerability
History
Type Values Removed Values Added
CPEs cpe:2.3:a:coredns.io:coredns:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Coredns.io
Coredns.io coredns
Vendors & Products Coredns.io
Coredns.io coredns
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
Title CoreDNS Loop Detection Denial of Service Vulnerability
Weaknesses CWE-337
CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-1241

    Use of Predictable Algorithm in Random Number Generator

  • CWE-337

    Predictable Seed in Pseudo-Random Number Generator (PRNG)

  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 1:15 AM
Reserved
Feb 9, 2026, 9:36 PM
Status
Modified
Published
Mar 6, 2026, 4:16 PM
Modified
Jul 15, 2026, 2:18 AM
Severity
Important
Public date
Mar 6, 2026, 3:35 PM