CVE-2026-35579General(coredns.io / coredns)

LOWCVSS 9.8 · CRITICAL

Signal is active with 3 mentions in latest observed window

Immediate actions

  • Patch coredns.io coredns systems immediately

Recommended action window: Monitor and triage in normal cycle

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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-287CWE-303

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • coredns

Threat summary

  • Patch or workaround signal is available
  • 6 mentions across 3 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 5 signals
  • General: 3 classified signals
  • Disclosure: 2 classified signals
  • Peaked at 3 mentions on most recent observed day (2026-05-12)
  • 6 total mentions across 3 days

Affected systems

Vendors
Products
coredns

Deep dive

Activity timeline6 mentions / 3d
01223Mentions · 2026-05-05: 2Mentions · 2026-05-06: 1Mentions · 2026-05-12: 3Patch / Workaround · 2026-05-05: 1Technical Details · 2026-05-05: 2Technical Details · 2026-05-06: 1Technical Details · 2026-05-12: 205-0505-0605-12
Signal classification3 categories
General
350.0%
Disclosure
233.3%
Patch
116.7%
Referenced assets5 URLs
Classification over time
DateTotalLabels
2026-05-052
Disclosure1Patch1
2026-05-061
Disclosure1
2026-05-123
General3
Full discourse6 posts
  • Lyrie.ai@lyrie_ai
    General

    CVE: CVE-2026-35579 CVSS: 9.8 (3.1) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Severity: CRITICAL Status: Critical advisory CoreDNS is a DNS server written in Go.

    Post summary

    The post merely announces a critical CVE for CoreDNS with CVSS details, but offers no proof of concept, exploit, or resolution information.

    1000037
    210 followersView on X
  • Lyrie.ai@lyrie_ai
    General

    CVSS 9.8 CRITICAL · CVE-2026-35579 · 9.8 → 1.14.3 CVE: CVE-2026-35579 CVSS: 9.8 (3.1) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Severity: CRITICAL Status: Critical advisory

    Post summary

    The snippet announces CVE-2026-35579 with a critical CVSS score and severity but provides no information on exploits, patches, or active use.

    1000047
    210 followersView on X
  • Lyrie.ai@lyrie_ai
    General

    https://lyrie.ai/research/research/cve-2026-35579-coredns-io-coredns #lyrie #cybersecurity #CVE #threatintel #zerodayattack

    Post summary

    The post merely shares a link and hashtags about CVE-2026-35579 with no additional information on the vulnerability, PoC, or mitigation.

    0000029
    210 followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-35579 TSIG Authentication Bypass in CoreDNS Versions Prior to 1.14.3 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-35579 Customizable Vulnerability Alerts: https://alerts.vulmon.com/?utm_source=twitter&utm_medium=social&utm_campaign=2102281&utm_content=4

    Post summary

    The post announces the TSIG authentication bypass vulnerability in CoreDNS versions before 1.14.3, providing basic technical details but no PoC, exploit code, patch, or exploitation evidence.

    0000046
    4.0K followersView on X
  • Infoflowcloud@infoflowcloud
    Disclosure

    🚨*CVE* 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. Fo… https://www.cve.org/CVERecord?id=CVE-2026-35579 ----- Traducción: CVE-2026-35579 Cor… http://infoflow.cloud`

    Post summary

    The post briefly announces CoreDNS CVE-2026-35579, noting a TSIG authentication flaw in versions before 1.14.3, and provides a link to the CVE record.

    0000064
    75 followersView on X
  • CVE@CVEnew
    Patch

    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. Fo… https://www.cve.org/CVERecord?id=CVE-2026-35579

    Post summary

    CoreDNS versions before 1.14.3 suffer from incorrect TSIG authentication handling; updating to 1.14.3 or later resolves the issue.

    00000255
    57.4K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appcoredns.iocoredns---

Explore more