CVE-2026-26018

HIGHPre-NVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
7.5
EG Score
7.5(low)
EPSS
60.7%
KEV
Not listed

Published

March 6, 2026

Last Modified

June 30, 2026

Advisory Details (7)

Auto-updated Jul 2, 2026
Patch available. Sources: github_release, github, redhat.
redhat

2445242 – (CVE-2026-26018) CVE-2026-26018 github.com/coredns/coredns: CoreDNS: Denial of Service vulnerability due to predictable pseudo-random number generation

https://bugzilla.redhat.com/show_bug.cgi?id=2445242
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-26018
github Patch Available

CoreDNS Loop Plugin DoS · Advisory · coredns/coredns · GitHub

https://github.com/coredns/coredns/security/advisories/GHSA-h75p-j8xm-m278
github_release Patch Available

v1.14.2

Patch available: coredns/coredns v1.14.2

https://github.com/coredns/coredns/releases/tag/v1.14.2

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/lighthouse-coredns-rhel9:17802042492026-06-10redhat
redhatrhacm2/lighthouse-coredns-rhel9:17740862252026-04-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/coredns/coredns1.14.2

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-01 15:06 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 04:40 UTCEG score recompute
  13. 2026-06-30 04:40 UTCVendor advisory
  14. 2026-06-30 04:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-26018?
CVE-2026-26018 is a high vulnerability published on March 6, 2026. 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…
When was CVE-2026-26018 disclosed?
CVE-2026-26018 was first published in the National Vulnerability Database on March 6, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26018 actively exploited?
CVE-2026-26018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-26018?
CVE-2026-26018 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-26018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26018

Explore →

Is Your Infrastructure Affected by CVE-2026-26018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.