CVE-2026-26018 Vulnerability Analysis & Exploit Details

CVE-2026-26018
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-26018 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-26018 Details

Status: Modified

Last updated: 🕐 09 Jul 2026, 13:16 UTC
Originally published on: 🕓 06 Mar 2026, 16:16 UTC

Time between publication and last update: 124 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-26018 Vulnerability Summary

CVE-2026-26018: 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.

Assessing the Risk of CVE-2026-26018

Access Complexity Graph

The exploitability of CVE-2026-26018 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-26018

With low attack complexity and no required privileges, CVE-2026-26018 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-26018, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-26018, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-26018 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-26018 poses no threat to data integrity.
  • Availability: High
    CVE-2026-26018 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-26018 References

External References

CWE Common Weakness Enumeration

CWE-1241

CAPEC Common Attack Pattern Enumeration and Classification

  • Cryptanalysis CAPEC-97 Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits).

Vulnerable Configurations

  • cpe:2.3:a:coredns.io:coredns:-:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:-:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:0.9.9:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:0.9.9:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:0.9.10:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:0.9.10:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:001:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:001:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.8:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.8:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.6.9:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.6.9:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.8.7:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.8.7:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.11.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.11.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.11.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.11.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.12.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.12.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.12.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.12.3:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.12.3:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.12.4:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.12.4:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.13.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.13.1:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.13.2:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.13.2:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:coredns.io:coredns:1.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:coredns.io:coredns:1.14.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-26018: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-15628 – A security flaw has been discovered in zhayujie chatgpt-on-wechat CowAgent up to 2.1.1. This issue affects the function Vision._download_to_data_ur...
  • CVE-2026-15627 – A vulnerability was identified in nextlevelbuilder GoClaw up to 3.13.3-beta.3. This vulnerability affects the function handleNavigate of the file p...
  • CVE-2026-15626 – A vulnerability was determined in nextlevelbuilder GoClaw 3.13.3-beta.3. This affects the function writeFile of the file internal/providers/acp/too...
  • CVE-2026-7640 – The WP Customer Area plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'type' attribute of the `customer-area-protected-con...
  • CVE-2026-15625 – A vulnerability was found in nextlevelbuilder GoClaw 3.11.3. Affected by this issue is the function ExecApprovalManager.CheckCommand of the file in...