CVE-2026-26018
CoreDNS Loop Detection Denial of Service Vulnerability
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
CoreDNS Loop Detection Denial of Service Vulnerability
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
CVE-2026-26018- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-337, CWE-770, CWE-400, CWE-1241
- Updated
- 2026-11-02
EUVDEUVD-2026-10043
7.5
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
EUVD-2026-10043- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-h75p-j8xm-m278
7.5
CoreDNS Loop Detection Denial of Service Vulnerability
Executive Summary
A Denial of Service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process.
Technical Details
Vulnerability Description
The CoreDNS loop plugin is designed to detect forwarding loops by performing a self-test during server startup. The plugin generates a random query name (qname) using Go's math/rand package and sends an HINFO query to itself. If the server receives multiple matching queries, it assumes a forwarding loop exists and terminates.
The vulnerability arises from two design flaws:
-
Predictable PRNG Seed: The random number generator is seeded with
time.Now().UnixNano(), making the generated qname predictable if an attacker knows the approximate server start time. -
Fatal Error Handler: When the plugin detects what it believes is a loop (3+ matching HINFO queries), it calls
log.Fatalf()which invokesos.Exit(1), immediately terminating the process without cleanup or recovery.
Affected Code
File: plugin/loop/setup.go
// PRNG seeded with predictable timestamp
var r = rand.New(time.Now().UnixNano())
// Qname generation using two consecutive PRNG calls
func qname(zone string) string {
l1 := strconv.Itoa(r.Int())
l2 := strconv.Itoa(r.Int())
return dnsutil.Join(l1, l2, zone)
}
File: plugin/loop/loop.go
func (l *Loop) ServeDNS(ctx context.Context, w dns.ResponseWriter, r *dns.Msg) (int, error) {
// ... validation checks ...
if state.Name() == l.qname {
l.inc() // Increment counter
}
if l.seen() > 2 {
// FATAL: Terminates entire process
log.Fatalf("Loop (%s -> %s) detected for zone %q...", ...)
}
// ...
}
File: plugin/pkg/log/log.go
func Fatalf(format string, v ...any) {
logf(fatal, format, v...)
os.Exit(1) // Immediate process termination
}
Exploitation Window
The loop plugin remains active during the following conditions:
| Condition | Window Duration | Attack Feasibility | |-----------|-----------------|-------------------| | Healthy startup | 2 seconds | Requires precise timing | | Self-test failure (upstream unreachable) | 30 seconds | HIGH - Extended window | | Network degradation | Variable | Depends on retry behavior |
Attack Scenario
Primary Attack Vector: Network Degradation
When the upstream DNS server is unreachable (network partition, misconfiguration, outage), the loop plugin's self-test fails repeatedly. During this period:
- The loop plugin remains active for up to 30 seconds
- Each self-test attempt generates an HINFO query visible in CoreDNS logs
- An attacker with log access (shared Kubernetes cluster, centralized logging) can observe the qname
- The attacker sends 3 HINFO queries with the observed qname
- The server immediately crashes
┌──────────────────────────────────────────────────────────────────────────┐
│ ATTACK TIMELINE │
├──────────────────────────────────────────────────────────────────────────┤
│ T+0s CoreDNS starts, PRNG seeded with UnixNano() │
│ T+0.5s Self-test HINFO query sent (visible in logs) │
│ T+2s Self-test fails (upstream timeout) │
│ T+3s Retry #1 - counter resets, qname unchanged │
│…
- Record
GHSA-h75p-j8xm-m278- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-337
- Updated
- 2026-11-02
NVD
7.5
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
CVE-2026-26018- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-337, CWE-400, CWE-770, CWE-1241
- Updated
- 2026-11-02
OSV
7.5
CoreDNS Loop Detection Denial of Service Vulnerability
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
CVE-2026-26018- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-337, CWE-400, CWE-770
- Updated
- 2026-11-02
OSVGHSA-h75p-j8xm-m278
7.5
CoreDNS Loop Detection Denial of Service Vulnerability
Executive Summary
A Denial of Service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process.
Technical Details
Vulnerability Description
The CoreDNS loop plugin is designed to detect forwarding loops by performing a self-test during server startup. The plugin generates a random query name (qname) using Go's math/rand package and sends an HINFO query to itself. If the server receives multiple matching queries, it assumes a forwarding loop exists and terminates.
The vulnerability arises from two design flaws:
-
Predictable PRNG Seed: The random number generator is seeded with
time.Now().UnixNano(), making the generated qname predictable if an attacker knows the approximate server start time. -
Fatal Error Handler: When the plugin detects what it believes is a loop (3+ matching HINFO queries), it calls
log.Fatalf()which invokesos.Exit(1), immediately terminating the process without cleanup or recovery.
Affected Code
File: plugin/loop/setup.go
// PRNG seeded with predictable timestamp
var r = rand.New(time.Now().UnixNano())
// Qname generation using two consecutive PRNG calls
func qname(zone string) string {
l1 := strconv.Itoa(r.Int())
l2 := strconv.Itoa(r.Int())
return dnsutil.Join(l1, l2, zone)
}
File: plugin/loop/loop.go
func (l *Loop) ServeDNS(ctx context.Context, w dns.ResponseWriter, r *dns.Msg) (int, error) {
// ... validation checks ...
if state.Name() == l.qname {
l.inc() // Increment counter
}
if l.seen() > 2 {
// FATAL: Terminates entire process
log.Fatalf("Loop (%s -> %s) detected for zone %q...", ...)
}
// ...
}
File: plugin/pkg/log/log.go
func Fatalf(format string, v ...any) {
logf(fatal, format, v...)
os.Exit(1) // Immediate process termination
}
Exploitation Window
The loop plugin remains active during the following conditions:
| Condition | Window Duration | Attack Feasibility | |-----------|-----------------|-------------------| | Healthy startup | 2 seconds | Requires precise timing | | Self-test failure (upstream unreachable) | 30 seconds | HIGH - Extended window | | Network degradation | Variable | Depends on retry behavior |
Attack Scenario
Primary Attack Vector: Network Degradation
When the upstream DNS server is unreachable (network partition, misconfiguration, outage), the loop plugin's self-test fails repeatedly. During this period:
- The loop plugin remains active for up to 30 seconds
- Each self-test attempt generates an HINFO query visible in CoreDNS logs
- An attacker with log access (shared Kubernetes cluster, centralized logging) can observe the qname
- The attacker sends 3 HINFO queries with the observed qname
- The server immediately crashes
┌──────────────────────────────────────────────────────────────────────────┐
│ ATTACK TIMELINE │
├──────────────────────────────────────────────────────────────────────────┤
│ T+0s CoreDNS starts, PRNG seeded with UnixNano() │
│ T+0.5s Self-test HINFO query sent (visible in logs) │
│ T+2s Self-test fails (upstream timeout) │
│ T+3s Retry #1 - counter resets, qname unchanged │
│…
- Record
GHSA-h75p-j8xm-m278- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-337
- Updated
- 2026-11-02
Show 8 moreShow less
OSVOESA-2026-3184
7.5
coredns security update
CoreDNS is a fast and flexible DNS server. The key word here is flexible: with CoreDNS you are able to do what you want with your DNS data by utilizing plugins.
Security Fix(es):
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.(CVE-2026-26018)
- Record
OESA-2026-3184- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVAZL-79500 No score
CVE-2026-26018 affecting package coredns for versions less than 1.11.4-15
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
AZL-79500- Updated
- 2026-11-05
OSVAZL-79529 No score
CVE-2026-26018 affecting package coredns 1.11.1-25
CoreDNS is a DNS server that chains plugins. Prior to version 1.14.2, a denial of service vulnerability exists in CoreDNS's loop detection plugin that allows an attacker to crash the DNS server by sending specially crafted DNS queries. The vulnerability stems from the use of a predictable pseudo-random number generator (PRNG) for generating a secret query name, combined with a fatal error handler that terminates the entire process. This issue has been patched in version 1.14.2.
- Record
AZL-79529- Updated
- 2026-11-02
OSVGO-2026-4635 No score
CoreDNS Loop Detection Denial of Service Vulnerability in github.com/coredns/coredns
CoreDNS Loop Detection Denial of Service Vulnerability in github.com/coredns/coredns
- Record
GO-2026-4635- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10297-1 No score
coredns-1.14.2-1.1 on GA media
These are all security issues fixed in the coredns-1.14.2-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10297-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20619-1 No score
Security update for coredns
This update for coredns fixes the following issues:
Changes in coredns:
-
Update to version 1.14.2:
- plugin/reload: Allow disabling jitter with 0s
- bump deps
- plugin/forward: fix parsing error when handling TLS+IPv6 address
- plugin/loop: use crypto/rand for query name generation
- plugin: reorder rewrite before acl to prevent bypass
- fix(rewrite): fix cname target rewrite for CNAME chains
- fix(kubernetes): panic on empty ListenHosts
- chore: bump minimum Go version to 1.25
- feat(proxyproto): add proxy protocol support
- refactor(cache): modernize with generics
- Add metadata for response Type and Class to Log
- docs: clarify kubernetes auth docs
- fix: return SOA and NS records when queried for a record CNAMEd to origin
-
fixes bsc#1259320 CVE-2026-26017
-
fixes bsc#1259319 CVE-2026-26018
-
address more unstable unstable tests under aarch64 and s390x
-
Update to version 1.14.1:
- This release primarily addresses security vulnerabilities affecting Go versions prior to Go 1.25.6 and Go 1.24.12 (CVE-2025-61728, CVE-2025-61726, CVE-2025-68121, CVE-2025-61731, CVE-2025-68119). It also includes performance improvements to the proxy plugin via multiplexed connections, along with various documentation updates.
- Record
openSUSE-SU-2026:20619-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:1042-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260317T205859 2026-03-17T20:58:59Z.
Refs jsc#PED-11136
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4360 CVE-2026-0528 GHSA-w2gr-585j-r428
- GO-2026-4513
- GO-2026-4514
- GO-2026-4518
- GO-2026-4526
- GO-2026-4549 CVE-2026-24005 GHSA-9fj4-3849-rv9g
- GO-2026-4550 CVE-2026-1229 GHSA-q9hv-hpm4-hj6x
- GO-2026-4551 CVE-2026-27575 GHSA-3ccg-x393-96v8
- GO-2026-4552 CVE-2026-27116 GHSA-4qgr-4h56-8895
- GO-2026-4553 CVE-2026-27616 GHSA-7jp5-298q-jg98
- GO-2026-4554 CVE-2026-27730 GHSA-p2v6-84h2-5x4r
- GO-2026-4556 CVE-2026-27819 GHSA-42wg-38gx-85rh
- GO-2026-4557 CVE-2026-26186 GHSA-49xw-vfc4-7p43
- GO-2026-4558 CVE-2026-27808 GHSA-mpf7-p9x7-96r3
- GO-2026-4560 CVE-2026-27465 GHSA-2v6m-6xw3-6467
- GO-2026-4561 CVE-2026-25963 GHSA-5jvp-m9h4-253h
- GO-2026-4562 CVE-2026-27900 GHSA-5rc7-2jj6-mp64
- GO-2026-4563 CVE-2026-24004 GHSA-9pm7-6g36-6j78
- GO-2026-4564 CVE-2026-23999 GHSA-ppwx-5jq7-px2w
- GO-2026-4565 CVE-2026-22728 GHSA-465p-v42x-3fmj
- GO-2026-4566 CVE-2026-27899 GHSA-5rmx-256w-8mj9
- GO-2026-4567 CVE-2026-27965 GHSA-8g8j-r87h-p36x
- GO-2026-4568 GHSA-gj6x-q8rh-wj6x
- GO-2026-4569 CVE-2026-27896 GHSA-wvj2-96wp-fq3f
- GO-2026-4570 CVE-2026-27969 GHSA-r492-hjgh-c9gw
- GO-2026-4571 CVE-2026-27734 GHSA-phwh-4f42-gwf3
- GO-2026-4572 CVE-2026-27946 GHSA-282g-fhmx-xf54
- GO-2026-4573 CVE-2026-27840 GHSA-6mq3-xmgp-pjm5
- GO-2026-4574 CVE-2026-27945 GHSA-7777-fhq9-592v
- GO-2026-4575 CVE-2026-28268 GHSA-rfjg-6m84-crj2
- GO-2026-4576 CVE-2026-28280 GHSA-4rv8-5cmm-2r22
- GO-2026-4577 CVE-2026-28407 GHSA-945p-3jhm-6rcp
- GO-2026-4578 CVE-2025-14443 GHSA-gxvv-45f6-3ch8
- GO-2026-4579 CVE-2026-28279 GHSA-rchw-322g-f7rm
- GO-2026-4580 CVE-2026-28406 GHSA-6rxq-q92g-4rmf
- GO-2026-4581 GHSA-xfx2-prg5-jq3g
- GO-2026-4583 GHSA-54p8-x2m9-c593
- GO-2026-4584 CVE-2026-28342 GHSA-pc8g-78pf-4xrp
- GO-2026-4585 CVE-2026-28492 GHSA-mr74-928f-rw69
- GO-2026-4586 CVE-2026-28789 GHSA-45m3-398w-m2m9
- GO-2026-4587 CVE-2026-28790 GHSA-4fqm-6fmh-82mq
- GO-2026-4588 CVE-2026-29049 GHSA-7rp8-r62p-q6wc
- GO-2026-4589 CVE-2021-25320 GHSA-gqf8-rvrh-g7w6
- GO-2026-4590 GHSA-hwm2-4ph6-w6m5
- GO-2026-4591 CVE-2025-62879 GHSA-wj3p-5h3x-c74q
- GO-2026-4592 CVE-2026-29073 GHSA-jqwg-75qf-vmf9
- GO-2026-4593 CVE-2026-26998 GHSA-fw45-f5q2-2p4x
- GO-2026-4594 CVE-2026-26999 GHSA-xw98-5q62-jx94
- GO-2026-4595 CVE-2026-3351 GHSA-crmg-9m86-636r
- GO-2026-4596 CVE-2026-29183 GHSA-6865-qjcf-286f
- GO-2026-4597 CVE-2026-29054 GHSA-92mv-8f8w-wq52
- GO-2026-4598 CVE-2026-29042 GHSA-95fj-3w7g-4r27
- GO-2026-4599 CVE-2026-27137
- GO-2026-4600 CVE-2026-27138
- GO-2026-4601 CVE-2026-25679
- GO-2026-4602 CVE-2026-27139
- GO-2026-4603 CVE-2026-27142
- GO-2026-4604 CVE-2026-29193 GHSA-25rw-g6ff-fmg8
- GO-2026-4605 CVE-2026-29192 GHSA-6rx5-m2rc-hmf7
- GO-2026-4606 CVE-2026-29188 GHSA-79pf-vx4x-7jmm
- GO-2026-4607 CVE-2026-29191 GHSA-pr34-2v5x-6qjq
- GO-2026-4608 CVE-2026-29771 GHSA-rhr9-hgcm-x289
- GO-2026-4609 CVE-2026-29781 GHSA-hx52-cv84-jr5v
- GO-2026-4610 CVE-2025-15558 GHSA-p436-gjf2-799p
- GO-2026-4612 CVE-2026-28683 GHSA-3c22-5j5m-4jq7
- GO-2026-4613 CVE-2026-28682 GHSA-c36c-7pc2-f2ph
- GO-2026-4614 CVE-2026-27944 GHSA-g9w5-qffc-6762
- GO-2026-4615 CVE-2026-29060 GHSA-m2hx-wjxc-9fp4
- GO-2026-4616 CVE-2026-25921 GHSA-cj4v-437j-jq4c
- GO-2026-4617 CVE-2026-26194 GHSA-v9vm-r24h-6rqm
- GO-2026-4618 CVE-2026-26195 GHSA-vgvf-m4fw-938j
- GO-2026-4619 CVE-2026-26196 GHSA-x9p5-w45c-7ffc
- GO-2026-4620 CVE-2026-26022 GHSA-xrcr-gmf5-2r8j
- GO-2026-4621 GHSA-fwhj-785h-43hh
- GO-2026-4622 CVE-2026-30223 GHSA-g962-2j28-3cg9
- GO-2026-4623 CVE-2026-30224 GHSA-gq2m-77hf-vwgh
- GO-2026-4624 CVE-2026-29084 GHSA-hcff-qv74-7hr4
- GO-2026-4625 CVE-2026-30225 GHSA-p443-p7w5-2f7f
- GO-2026-4626 CVE-2026-29061…
- Record
SUSE-SU-2026:1042-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/coredns/corednsGo |
before 1.14.2 | 1.14.2 |
corednsAzure Linux:3 |
before 1.11.4-15 | 1.11.4-15 |
corednsAzure Linux:2 |
through 1.11.1-25 | None known |
corednsopenEuler:24.03-LTS-SP4 |
before 1.7.0-1.7.oe2403sp4 | 1.7.0-1.7.oe2403sp4 |
corednsopenEuler:20.03-LTS-SP4 |
before 1.7.0-1.5.oe2003sp4 | 1.7.0-1.5.oe2003sp4 |
corednsopenEuler:22.03-LTS-SP4 |
before 1.7.0-1.7.oe2203sp4 | 1.7.0-1.7.oe2203sp4 |
corednsopenEuler:24.03-LTS-SP1 |
before 1.7.0-1.7.oe2403sp1 | 1.7.0-1.7.oe2403sp1 |
corednsopenEuler:24.03-LTS-SP3 |
before 1.7.0-1.7.oe2403sp3 | 1.7.0-1.7.oe2403sp3 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 124 CVEs |
before 0.0.20260317T205859-150000.1.152.1 | 0.0.20260317T205859-150000.1.152.1 |
corednsopenSUSE:Tumbleweed From an advisory covering 2 CVEs |
before 1.14.2-1.1 | 1.14.2-1.1 |
corednsopenSUSE:Leap 16.0 From an advisory covering 7 CVEs |
before 1.14.2-bp160.1.1 | 1.14.2-bp160.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| facts | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-26018 is a high vulnerability (CVSS 7.5) in Coredns, published March 6, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.24%, the 69th percentile. Fixed in github.com/coredns/coredns 1.14.2.
References
github.com/coredns/coredns/security/advisories/GHSA-h75p-j8xm-m278
github.com/coredns/coredns/releases/tag/v1.14.2
access.redhat.com/security/cve/CVE-2026-26018
bugzilla.redhat.com/show_bug.cgi?id=2445242
security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-26018.json
access.redhat.com/errata/RHSA-2026:36873
Show 194 moreShow less
access.redhat.com/errata/RHSA-2026:25127
access.redhat.com/errata/RHSA-2026:8151
nvd.nist.gov/vuln/detail/CVE-2026-26018
github.com/advisories/GHSA-h75p-j8xm-m278
github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26018.json
github.com/coredns/coredns
openeuler.org/zh/security/security-bulletins/detail?id=openEuler-SA-2026-3184
suse.com/support/update/announcement/2026/suse-su-20261042-1
suse.com/security/cve/CVE-2021-25320
suse.com/security/cve/CVE-2025-14443
suse.com/security/cve/CVE-2025-15558
suse.com/security/cve/CVE-2025-62879
suse.com/security/cve/CVE-2026-0528
suse.com/security/cve/CVE-2026-1229
suse.com/security/cve/CVE-2026-22728
suse.com/security/cve/CVE-2026-23999
suse.com/security/cve/CVE-2026-24004
suse.com/security/cve/CVE-2026-24005
suse.com/security/cve/CVE-2026-25679
suse.com/security/cve/CVE-2026-25921
suse.com/security/cve/CVE-2026-25963
suse.com/security/cve/CVE-2026-26017
suse.com/security/cve/CVE-2026-26018
suse.com/security/cve/CVE-2026-26022
suse.com/security/cve/CVE-2026-26186
suse.com/security/cve/CVE-2026-26194
suse.com/security/cve/CVE-2026-26195
suse.com/security/cve/CVE-2026-26196
suse.com/security/cve/CVE-2026-26276
suse.com/security/cve/CVE-2026-26998
suse.com/security/cve/CVE-2026-26999
suse.com/security/cve/CVE-2026-27116
suse.com/security/cve/CVE-2026-27137
suse.com/security/cve/CVE-2026-27138
suse.com/security/cve/CVE-2026-27139
suse.com/security/cve/CVE-2026-27142
suse.com/security/cve/CVE-2026-27465
suse.com/security/cve/CVE-2026-27575
suse.com/security/cve/CVE-2026-27616
suse.com/security/cve/CVE-2026-27730
suse.com/security/cve/CVE-2026-27734
suse.com/security/cve/CVE-2026-27808
suse.com/security/cve/CVE-2026-27819
suse.com/security/cve/CVE-2026-27840
suse.com/security/cve/CVE-2026-27896
suse.com/security/cve/CVE-2026-27899
suse.com/security/cve/CVE-2026-27900
suse.com/security/cve/CVE-2026-27944
suse.com/security/cve/CVE-2026-27945
suse.com/security/cve/CVE-2026-27946
suse.com/security/cve/CVE-2026-27965
suse.com/security/cve/CVE-2026-27969
suse.com/security/cve/CVE-2026-2808
suse.com/security/cve/CVE-2026-28229
suse.com/security/cve/CVE-2026-28268
suse.com/security/cve/CVE-2026-28279
suse.com/security/cve/CVE-2026-28280
suse.com/security/cve/CVE-2026-28342
suse.com/security/cve/CVE-2026-28406
suse.com/security/cve/CVE-2026-28407
suse.com/security/cve/CVE-2026-28492
suse.com/security/cve/CVE-2026-28512
suse.com/security/cve/CVE-2026-28513
suse.com/security/cve/CVE-2026-28682
suse.com/security/cve/CVE-2026-28683
suse.com/security/cve/CVE-2026-28789
suse.com/security/cve/CVE-2026-28790
suse.com/security/cve/CVE-2026-29042
suse.com/security/cve/CVE-2026-29049
suse.com/security/cve/CVE-2026-29054
suse.com/security/cve/CVE-2026-29060
suse.com/security/cve/CVE-2026-29061
suse.com/security/cve/CVE-2026-29064
suse.com/security/cve/CVE-2026-29073
suse.com/security/cve/CVE-2026-29084
suse.com/security/cve/CVE-2026-29183
suse.com/security/cve/CVE-2026-29188
suse.com/security/cve/CVE-2026-29191
suse.com/security/cve/CVE-2026-29192
suse.com/security/cve/CVE-2026-29193
suse.com/security/cve/CVE-2026-29194
suse.com/security/cve/CVE-2026-29195
suse.com/security/cve/CVE-2026-29196
suse.com/security/cve/CVE-2026-29771
suse.com/security/cve/CVE-2026-29773
suse.com/security/cve/CVE-2026-29777
suse.com/security/cve/CVE-2026-29781
suse.com/security/cve/CVE-2026-30223
suse.com/security/cve/CVE-2026-30224
suse.com/security/cve/CVE-2026-30225
suse.com/security/cve/CVE-2026-30233
suse.com/security/cve/CVE-2026-30247
suse.com/security/cve/CVE-2026-30832
suse.com/security/cve/CVE-2026-30834
suse.com/security/cve/CVE-2026-30851
suse.com/security/cve/CVE-2026-30852
suse.com/security/cve/CVE-2026-30855
suse.com/security/cve/CVE-2026-30856
suse.com/security/cve/CVE-2026-30857
suse.com/security/cve/CVE-2026-30858
suse.com/security/cve/CVE-2026-30859
suse.com/security/cve/CVE-2026-30860
suse.com/security/cve/CVE-2026-30861
suse.com/security/cve/CVE-2026-30869
suse.com/security/cve/CVE-2026-30914
suse.com/security/cve/CVE-2026-30915
suse.com/security/cve/CVE-2026-30926
suse.com/security/cve/CVE-2026-30933
suse.com/security/cve/CVE-2026-30934
suse.com/security/cve/CVE-2026-30943
suse.com/security/cve/CVE-2026-30955
suse.com/security/cve/CVE-2026-30961
suse.com/security/cve/CVE-2026-31801
suse.com/security/cve/CVE-2026-31807
suse.com/security/cve/CVE-2026-31809
suse.com/security/cve/CVE-2026-31817
suse.com/security/cve/CVE-2026-31863
suse.com/security/cve/CVE-2026-31866
suse.com/security/cve/CVE-2026-31886
suse.com/security/cve/CVE-2026-31892
suse.com/security/cve/CVE-2026-31959
suse.com/security/cve/CVE-2026-31960
suse.com/security/cve/CVE-2026-31961
suse.com/security/cve/CVE-2026-32102
suse.com/security/cve/CVE-2026-32110
suse.com/security/cve/CVE-2026-32136
suse.com/security/cve/CVE-2026-32245
suse.com/security/cve/CVE-2026-32246
suse.com/security/cve/CVE-2026-32319
suse.com/security/cve/CVE-2026-32320
suse.com/security/cve/CVE-2026-32614
suse.com/security/cve/CVE-2026-3351
bugzilla.suse.com/1259319
bugzilla.suse.com/1259320
suse.com/security/cve/CVE-2025-61726
suse.com/security/cve/CVE-2025-61728
suse.com/security/cve/CVE-2025-61731
suse.com/security/cve/CVE-2025-68119
suse.com/security/cve/CVE-2025-68121
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
suse.com/security/cve/CVE-2016-11068
suse.com/security/cve/CVE-2016-11069
suse.com/security/cve/CVE-2016-11070
suse.com/security/cve/CVE-2016-11071
suse.com/security/cve/CVE-2016-11072
suse.com/security/cve/CVE-2016-11073
suse.com/security/cve/CVE-2016-11074
suse.com/security/cve/CVE-2016-11075
suse.com/security/cve/CVE-2016-11076
suse.com/security/cve/CVE-2016-11077
suse.com/security/cve/CVE-2016-11078
suse.com/security/cve/CVE-2016-11079
suse.com/security/cve/CVE-2016-11080
suse.com/security/cve/CVE-2016-11081
suse.com/security/cve/CVE-2016-11082
suse.com/security/cve/CVE-2016-11083
suse.com/security/cve/CVE-2016-11084
suse.com/security/cve/CVE-2017-18870
suse.com/security/cve/CVE-2017-18871
suse.com/security/cve/CVE-2017-18872
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18874
suse.com/security/cve/CVE-2017-18875
suse.com/security/cve/CVE-2017-18876
suse.com/security/cve/CVE-2017-18877
suse.com/security/cve/CVE-2017-18878
suse.com/security/cve/CVE-2017-18879
suse.com/security/cve/CVE-2017-18883
suse.com/security/cve/CVE-2017-18884
suse.com/security/cve/CVE-2017-18885
suse.com/security/cve/CVE-2017-18886
suse.com/security/cve/CVE-2017-18887
suse.com/security/cve/CVE-2017-18888
suse.com/security/cve/CVE-2017-18889
suse.com/security/cve/CVE-2017-18890
suse.com/security/cve/CVE-2017-18891
suse.com/security/cve/CVE-2017-18892
suse.com/security/cve/CVE-2017-18893
suse.com/security/cve/CVE-2017-18894
suse.com/security/cve/CVE-2017-18895
suse.com/security/cve/CVE-2017-18896
suse.com/security/cve/CVE-2017-18897
suse.com/security/cve/CVE-2017-18898
suse.com/security/cve/CVE-2017-18900
suse.com/security/cve/CVE-2017-18901
suse.com/security/cve/CVE-2017-18902
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18904
suse.com/security/cve/CVE-2017-18905
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
Left out here: 1,550 references and the rest of 4 source descriptions. The JSON record has them.