BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-86003High confidence

CoreDNS DoH/DoQ/gRPC bypass UPDATE rejection enforced on UDP/TCP

coredns · coredns

Official source article: GitHub GHSA-9GM5-9RFH-M6VX ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.44% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs coredns coredns and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Open-source package ranges3 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/coredns/corednsSEMVER: introduced 0; fixed 1.14.71.14.7OSV record ↗aggregator derived · 28 Sep 2026
Gogithub.com/coredns/corednsSEMVER: introduced 0; fixed 1.14.71.14.7OSV record ↗aggregator derived · 28 Sep 2026
gogithub.com/coredns/coredns<= 1.14.61.14.7GitHub advisory ↗upstream repository advisory · 17 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-86003 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/coredns/coredns: CoreDNS: Unauthorized DNS record modification via unvalidated DNS updates
3 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • rhcl-1/coredns-rhel9 as a component of Red Hat Connectivity Link 1
  • openshift4/ose-coredns as a component of Red Hat OpenShift Container Platform 4
  • openshift4/ose-coredns-rhel9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in CoreDNS. The DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners do not properly validate incoming DNS update requests. An unauthenticated client can send a specially crafted DNS update (RFC 2136 UPDATE) that CoreDNS forwards to an upstream DNS server. If the upstream server trusts CoreDNS, this can lead to unauthorized modification, addition, or deletion of DNS records, potentially redirecting traffic or disrupting the DNS zone.
Remediation
Until updates are available, administrators can implement the following mitigations to prevent DNS UPDATE proxying attacks: 1. If DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, or DNS-over-gRPC are not required, disable these custom transport protocols. Standard UDP and TCP DNS listeners are not affected by this vulnerability. 2. Configure upstream authoritative DNS servers to reject UPDATE messages that lack a valid end-to-end TSIG (Transaction Signature) cryptographic signature, regardless of source IP address trust. 3. Review upstream DNS server ACLs to ensure CoreDNS does not have unnecessary write permissions to authoritative zones. Apply principle of least privilege. 4. If CoreDNS must forward to authoritative servers, implement network segmentation and firewall rules to restrict which DNS UPDATE operations can reach upstream servers. 5. Monitor DNS zone change logs on authoritative servers for unexpected UPDATE operations originating from CoreDNS IP addresses. Apply updates as they become available from Red Hat product teams. For OpenShift clusters, prioritize patching environments that forward DNS queries to internal authoritative DNS servers with UPDATE support enabled.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-80989

No EUVD known-exploited evidence

CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack without the dns.DefaultMsgAcceptFunc request policy used by UDP, TCP, and DNS-over-TLS. An unauthenticated client can send an RFC 2136 UPDATE that the proxy or forward plugin passes unchanged to an update-capable upstream. If that upstream trusts CoreDNS's source address or connection and does not require an attacker-unknown end-to-end TSIG, the request appears to originate from CoreDNS and can add, replace, or delete DNS records, redirect traffic, take over names, alter mail routing, or disrupt the writable zone. This issue is fixed in version 1.14.7.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack without the dns.DefaultMsgAcceptFunc request policy used by UDP, TCP, and DNS-over-TLS. An unauthenticated client can send an RFC 2136 UPDATE that the proxy or forward plugin passes unchanged to an update-capable upstream. If that upstream trusts CoreDNS's source address or connection and does not require an attacker-unknown end-to-end TSIG, the request appears to originate from CoreDNS and can add, replace, or delete DNS records, redirect traffic, take over names, alter mail routing, or disrupt the writable zone. This issue is fixed in version 1.14.7.

What

CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack without the dns.DefaultMsgAcceptFunc request policy used by UDP, TCP, and DNS-over-TLS. An unauthenticated client can send an RFC 2136 UPDATE that the proxy or forward plugin passes unchanged to an update-capable upstream. If that upstream trusts CoreDNS's source address or connection and does not require an attacker-unknown end-to-end TSIG, the request appears to originate from CoreDNS and can add, replace, or delete DNS records, redirect traffic, take over names, alter mail routing, or disrupt the writable zone. This issue is fixed in version 1.14.7.

Why

The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack without the dns.DefaultMsgAcceptFunc request policy used by UDP, TCP, and DNS-over-TLS. An unauthenticated client can send an RFC 2136 UPDATE that the proxy or forward plugin passes unchanged to an update-capable upstream. If that upstream trusts CoreDNS's source address or connection and does not require an attacker-unknown end-to-end TSIG, the request appears to originate from CoreDNS and can add, replace, or delete DNS records, redirect traffic, take over names, alter mail routing, or disrupt the writable zone. This issue is fixed in version 1.14.7.

Why

The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Unintended Proxy or Intermediary ('Confused Deputy') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-441 ↗

CWE-441: Unintended Proxy or Intermediary ('Confused Deputy'). The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-441
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-80989Official EUVD mapping

CoreDNS is a DNS server written in Go. Prior to 1.14.7, the DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, and DNS-over-gRPC listeners in plugin/pkg/doh/doh.go, core/dnsserver/server_quic.go, and core/dnsserver/server_grpc.go call dns.Msg.Unpack without the dns.DefaultMsgAcceptFunc request policy used by UDP, TCP, and DNS-over-TLS. An unauthenticated client can send an RFC 2136 UPDATE that the proxy or forward plugin passes unchanged to an update-capable upstream. If that upstream trusts CoreDNS's source address or connection and does not require an attacker-unknown end-to-end TSIG, the request appears to originate from CoreDNS and can add, replace, or delete DNS records, redirect traffic, take over names, alter mail routing, or disrupt the writable zone. This issue is fixed in version 1.14.7.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3198CoreDNS: Schwachstelle ermöglicht Manipulation von DNS Einträgen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in CoreDNS ausnutzen, um DNS Einträge zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260923Security Bulletin 23 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Sep 2026, published on 23 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
1.14.7.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Until updates are available, administrators can implement the following mitigations to prevent DNS UPDATE proxying attacks: 1. If DNS-over-HTTPS, DNS-over-HTTP/3, DNS-over-QUIC, or DNS-over-gRPC are not required, disable these custom transport protocols. Standard UDP and TCP DNS listeners are not affected by this vulnerability. 2. Configure upstream authoritative DNS servers to reject UPDATE messages that lack a valid end-to-end TSIG (Transaction Signature) cryptographic signature, regardless of source IP address trust. 3. Review upstream DNS server ACLs to ensure CoreDNS does not have unnecessary write permissions to authoritative zones. Apply principle of least privilege. 4. If CoreDNS must forward to authoritative servers, implement network segmentation and firewall rules to restrict which DNS UPDATE operations can reach upstream servers. 5. Monitor DNS zone change logs on authoritative servers for unexpected UPDATE operations originating from CoreDNS IP addresses. Apply updates as they become available from Red Hat product teams. For OpenShift clusters, prioritize patching environments that forward DNS queries to internal authoritative DNS servers with UPDATE support enabled.
04

Evidence and provenance

Published 16 Sept 2026 · Last source change 17 Sept 2026, 19:25 UTC · CWE-441 · Unintended Proxy or Intermediary ('Confused Deputy')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-17
European sourceENISA EUVD · EUVD-2026-80989
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhacm2/lighthouse-coredns-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhcl-1/coredns-rhel9 as a component of Red Hat Connectivity Link 1; openshift4/ose-coredns as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-coredns-rhel9 as a component of Red Hat OpenShift Container Platform 4
    After
    rhcl-1/coredns-rhel9 as a component of Red Hat Connectivity Link 1; openshift4/ose-coredns as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-coredns-rhel9 as a component of Red Hat OpenShift Container Platform 4
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-86003 to remediation: access.redhat.com/CVE-2026-86003.
    Before
    remediation: access.redhat.com/CVE-2026-86003
    After
    remediation: access.redhat.com/CVE-2026-86003
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    rhacm2/lighthouse-agent-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhacm2/lighthouse-coredns-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhcl-1/coredns-rhel9 as a component of Red Hat Connectivity Link 1; openshift4/ose-coredns as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-coredns-rhel9 as a component of Red Hat OpenShift Container Platform 4
    After
    rhacm2/lighthouse-coredns-rhel9 as a component of Red Hat Advanced Cluster Management for Kubernetes 2; rhcl-1/coredns-rhel9 as a component of Red Hat Connectivity Link 1; openshift4/ose-coredns as a component of Red Hat OpenShift Container Platform 4; openshift4/ose-coredns-rhel9 as a component of Red Hat OpenShift Container Platform 4
    Red Hat Product Security ↗
  5. ENISA EUVD mappingEUVD-2026-80989 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-80989"}
    ENISA EUVD ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-80989↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-9GM5-9RFH-M6VX↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-86003 · cve.blacktree.nl