Skip to main content
Public proof of conceptFix available

CVE-2026-35579

A public proof of concept exists; no exploitation attested.

  • Published2026-05-05
  • Fixed in1.14.3
  • WeaknessCWE-287 · CWE-303

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-05-0521:16CVE publishedNVD

Versions per branch

NVD · OSV
Coredns.io coredns
BranchAffectedFixed in
1.14< 1.14.31.14.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • coredns
    Affected
    • = < 1.14.3no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-05-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • corednsopenEuler:24.03-LTS-SP4all versions · fixed in 1.7.0-1.8.oe2403sp4
  • corednsopenEuler:24.03-LTS-SP3all versions · fixed in 1.7.0-1.8.oe2403sp3
  • corednsopenEuler:24.03-LTS-SP1all versions · fixed in 1.7.0-1.8.oe2403sp1
  • corednsopenEuler:22.03-LTS-SP4all versions · fixed in 1.7.0-1.8.oe2203sp4
  • corednsopenEuler:20.03-LTS-SP4all versions · fixed in 1.7.0-1.6.oe2003sp4
  • corednsCleanStartall versions · fixed in 1.14.2-r1and 1 other package
  • corednsAzure Linux:3all versions · fixed in 1.11.4-16
  • coredns-1.11MinimOSall versions · no fixed version listedand 42 other packages

27 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-35579 Red Hat Product Security8 products fixed

    github.com/coredns/coredns: CoreDNS: Authentication bypass allows unauthorized access to TSIG-protected functionalities

  • RHSA-2026:85227 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Submariner v0.23 security fixes and container updates

  • RHSA-2026:25127 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Submariner v0.21 security fixes and container updates

Full record on NVD

Fix

  1. Update Coredns.io coredns to 1.14.3
  2. Vendor fix Red Hat Product Security RHSA-2026:85227 · 4 productsFor release note details, see the upstream Submariner release notes: https://submariner.io/community/releases/ Downstream-specific issues resolved: * ACM-34110 * ACM-34588 * ACM-28591 * ACM-34578 * ACM-40464 * ACM-38424 * ACM-38427 * ACM-38429 * ACM-38430 * ACM-38431 * ACM-38434 * ACM-38439 * ACM…
  3. Vendor fix Red Hat Product Security RHSA-2026:25127 · 4 productsFor release note details, see the upstream Submariner release notes: https://submariner.io/community/releases/ Downstream-specific issues resolved: * ACM-27238 * ACM-28294 * ACM-28295 * ACM-28311 * ACM-28313 * ACM-28314 * ACM-28315 * ACM-28316 * ACM-28329 * ACM-28331 * ACM-28333 * ACM-28335 * ACM…

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-05-05
Last Modified
2026-07-24
NVD status
Modified
MSRC Title
CoreDNS TSIG authentication bypass on gRPC, QUIC, DoH, and DoH3 transports
GitHub Advisory
GHSA-vp29-5652-4fw9

Frequently asked questions

What is CVE-2026-35579?

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.

Is CVE-2026-35579 actively exploited?

A proof-of-concept exploit exists for CVE-2026-35579, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-35579?

CVE-2026-35579 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running coredns/coredns? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record