Bug 2466856 (CVE-2026-33190)

Summary: CVE-2026-33190 github.com/coredns/coredns: CoreDNS: Authentication bypass via flawed TSIG plugin verification on non-plain-DNS transports
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: alcohan, gparvin, jbalunas, pahickey, rhaigner
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in CoreDNS, a DNS server that chains plugins. An unauthenticated remote client can bypass TSIG (Transaction Signature) based authentication on non-plain-DNS transports such as DNS over TLS (DoT), DNS over HTTPS (DoH), DNS over HTTP/3 (DoH3), DNS over QUIC (DoQ), and gRPC. This bypass occurs because the `tsig` plugin incorrectly trusts the transport writer's status instead of performing its own verification. This allows unauthorized access to resources that should be restricted by TSIG policies.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-05-05 20:01:36 UTC
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.