CVE-2026-33190 Vulnerability Analysis & Exploit Details

CVE-2026-33190
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-33190 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-33190 Details

Status: Analyzed

Last updated: 🕓 08 May 2026, 16:01 UTC
Originally published on: 🕗 05 May 2026, 20:16 UTC

Time between publication and last update: 2 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-33190 Vulnerability Summary

CVE-2026-33190: CoreDNS is a DNS server that chains plugins. In versions prior to 1.14.3, the tsig plugin can be bypassed on non-plain-DNS transports (DoT, DoH, DoH3, DoQ, and gRPC) because it trusts the transport writer's TsigStatus() instead of performing verification itself. The DoH and DoH3 writer's TsigStatus() always returns nil, the DoT server does not set TsigSecret on the dns.Server, and the DoQ and gRPC writers also unconditionally return nil. This allows an unauthenticated remote client to bypass TSIG-based authentication and access resources intended to be restricted behind a tsig require all policy. Plain DNS over TCP and UDP are not affected. This issue has been fixed in version 1.14.3.

Assessing the Risk of CVE-2026-33190

Access Complexity Graph

The exploitability of CVE-2026-33190 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-33190

With low attack complexity and no required privileges, CVE-2026-33190 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-33190, 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-33190, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-33190 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-33190 poses no threat to data integrity.
  • Availability: None
    CVE-2026-33190 does not impact system availability.

CVE-2026-33190 References

External References

CWE Common Weakness Enumeration

CWE-303

CAPEC Common Attack Pattern Enumeration and Classification

  • Reflection Attack in Authentication Protocol CAPEC-90 An adversary can abuse an authentication protocol susceptible to reflection attack in order to defeat it. Doing so allows the adversary illegitimate access to the target system, without possessing the requisite credentials. Reflection attacks are of great concern to authentication protocols that rely on a challenge-handshake or similar mechanism. An adversary can impersonate a legitimate user and can gain illegitimate access to the system by successfully mounting a reflection attack during authentication.

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:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-33190: 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-8288 – A vulnerability was determined in Open5GS up to 2.7.7. This affects the function gsm_handle_pdu_session_modification_qos_flow_descriptions of the f...
  • CVE-2025-9973 – Due to not validating the organization context when executing adaptive authentication flows, the WSO2 Identity Server allows adaptive authenticatio...
  • CVE-2025-10470 – The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to ...
  • CVE-2026-6956 – ATutor is vulnerable to Reflected XSS in /install/install.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...
  • CVE-2026-6909 – ATutor is vulnerable to Reflected XSS in /install/upgrade.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...