Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
CoreDNS and DNS cache packages may return wrong addresses
published 1 month ago
Summary
The CoreDNS and Kubernetes DNS node‑cache packages can be manipulated to provide incorrect DNS results, potentially directing users to malicious sites. This risk is fixed in newer releases of these packages. Update CoreDNS and all Kubernetes DNS node‑cache components to the latest available versions as soon as possible.
What to do
- Update cleanstart coredns to version 1.14.2-r1.
- Update cleanstart kubernetes-dns-node-cache to version 1.23.1-r0.
- Update cleanstart kubernetes-dns-node-cache to version 1.24.1-r1.
- Update cleanstart kubernetes-dns-node-cache to version 1.25.0-r8.
- Update cleanstart kubernetes-dns-node-cache to version 1.26.0-r1.
- Update cleanstart kubernetes-dns-node-cache-fips to version 1.26.0-r1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| CleanStart | cleanstart | coredns |
< 1.14.2-r1 Fix: upgrade to 1.14.2-r1
|
| CleanStart | cleanstart | kubernetes-dns-node-cache |
< 1.23.1-r0 < 1.24.1-r1 < 1.25.0-r8 < 1.26.0-r1 Fix: upgrade to 1.23.1-r0
|
| CleanStart | cleanstart | kubernetes-dns-node-cache-fips |
< 1.26.0-r1 Fix: upgrade to 1.26.0-r1
|
Original advisory text
Security fix for CVE-2026-35579 applied in: coredns 1.14.2-r1, kubernetes-dns-node-cache 1.23.1-r0, kubernetes-dns-node-cache 1.24.1-r1, kubernetes-dns-node-cache 1.25.0-r8, kubernetes-dns-node-cache 1.26.0-r1, kubernetes-dns-node-cache-fips 1.26.0-r1
CVE-2026-35579 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.
Timeline
Published18 Sep 2026
Updated18 Sep 2026
First seen18 Sep 2026
Sources
CLEANSTART-2026-LE40219 · OSV
Track software like this
Free during beta