CVE-2026-26018
Coredns.io Coredns denial of service
- Published6 Mar 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:25127
- https://access.redhat.com/errata/RHSA-2026:36873
- https://access.redhat.com/errata/RHSA-2026:8151
- https://access.redhat.com/security/cve/CVE-2026-26018
- https://bugzilla.redhat.com/show_bug.cgi?id=2445242
- https://github.com/coredns/coredns/releases/tag/v1.14.2
- https://github.com/coredns/coredns/security/advisories/GHSA-h75p-j8xm-m278
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-26018.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-26018 being actively exploited?
CVE-2026-26018 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.79%.
How severe is CVE-2026-26018?
CVE-2026-26018 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.79% probability of exploitation.
Which products are affected by CVE-2026-26018?
Affected products include Coredns.io Coredns.
How do I fix CVE-2026-26018?
Upgrade affected software to a fixed version, for example Coredns.io Coredns 1.14.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-26018 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.