Summary
generated automatically from NVD dataCoreDNS versions prior to 1.14.3 mishandle TSIG authentication on the gRPC, QUIC, DoH, and DoH3 transports. The gRPC and QUIC paths never validate the HMAC, and the DoH and DoH3 paths treat any request carrying a TSIG record as authenticated, letting an unauthenticated network attacker bypass TSIG-protected features such as AXFR/IXFR zone transfers and dynamic DNS updates. The issue is rated CRITICAL (CVSS 9.8) and is fixed in 1.14.3; disabling the affected listeners or restricting access to trusted sources is a workaround.
NVD description
CoreDNS is a DNS server written in Go. In versions prior to 1.14.3, the gRPC, QUIC, DoH, and DoH3 transport implementations incorrectly handle TSIG authentication. For gRPC and QUIC, the server checks whether the TSIG key name exists in the configuration but never calls dns.TsigVerify() to validate the HMAC. If the key name matches a configured key, the tsigStatus field remains nil and the tsig plugin treats the request as successfully authenticated regardless of the MAC value. For DoH and DoH3, the issue is more severe: the DoHWriter.TsigStatus() method unconditionally returns nil, and the server never inspects the TSIG record at all. Any request containing a TSIG record is treated as authenticated over DoH and DoH3, even if the key name is invalid and the MAC is arbitrary. An unauthenticated network attacker can exploit this to bypass TSIG-protected functionality such as AXFR/IXFR zone transfers, dynamic DNS updates, or other TSIG-gated plugin behavior. The DoH and DoH3 variants have a lower exploitation bar because the attacker does not need to know a valid TSIG key name. This issue has been fixed in version 1.14.3. As a workaround, disable gRPC, QUIC, DoH, and DoH3 listeners where TSIG authentication is required, or restrict network-level access to affected transport ports to trusted sources only.
EPSS · FIRST.org
0.75%probability of exploitation in the next 30 days
Higher than 54% of scored CVEs
EPSS (Exploit Prediction Scoring System) estimates, from observed exploitation activity, how likely a CVE is to be exploited in the next 30 days. It complements CVSS, which measures severity, not likelihood. Score of 2026-10-16, recomputed daily by FIRST.org.
In-depth analysis on cveo.tech
We've published a detailed analysis of this CVE — exploitation, IOCs and mitigation.
CVSS v3.1 Score
Information
- Published
- 5 mai 2026
- Updated
- 24 juil. 2026
- Status
- Modified
- Source
- security-advisories@github.com
Affected products
Weaknesses (CWE)
References (6)
- https://github.com/coredns/coredns/security/advisories/GHSA-vp29-5652-4fw9ExploitMitigationVendor Advisory
- https://github.com/coredns/coredns/security/advisories/GHSA-vp29-5652-4fw9ExploitMitigationVendor Advisory
Similar CVEs
Other vulnerabilities of type CWE-287
Monitor your products
Get automatic alerts for every new CVE affecting your equipment.