Skip to content
Fencer Intel
high 7.5

CVE-2026-86003 json

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

published last mo. modified last mo. also EUVD-2026-80989 , GHSA-9gm5-9rfh-m6vx , GO-2026-6506

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/coredns/coredns 1.14.7
  • coredns.io coredns 1.14.7
  • coredns Azure Linux 3.0 1.11.4-22

azure linux advisories AZL-101835

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-86003 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-86003 updated cvss 7.5

github.com/coredns/coredns: CoreDNS: Unauthorized DNS record modification via unvalidated DNS updates

  • Red Hat Connectivity Link 1 rhcl-1/coredns-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-coredns-rhel9
    affected: workaround, no fix available
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/lighthouse-agent-rhel9, rhacm2/lighthouse-coredns-rhel9 Red Hat OpenShift Container Platform 4 openshift4/ose-coredns Red Hat OpenShift Container Platform 5 openshift5/ose-coredns-rhel9
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/coredns/coredns
<1.14.7
1.14.7

Affected products

  • coredns coredns

Classification

Weakness
  • CWE-441 Unintended Proxy or Intermediary

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.