Vulnerability · openSUSE-SU-2026:22135-1
Security update for coredns
Published Oct 19, 2026 · catalog updated Oct 20, 2026 · Security update for coredns
Open the advisory
Exploitation likelihood is not on this record for openSUSE-SU-2026:22135-1. A missing EPSS score is not a low risk. Compare Security update for coredns with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Security update for coredns).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Advisory link
- Affected products
- openSUSE:Leap 16.0 coredns
This update for coredns fixes the following issues: Changes in coredns: - Bump vendored google.golang.org/grpc from 1.83.0 to 1.83.1: * CVE-2026-84304: heap memory exhaustion via HTTP/2 DATA frame fragmentation in the gRPC transport (boo#1279216) * Done through the go_modules "require" parameter in _service - Update license tag to Apache-2.0 AND MPL-2.0 * outcome of legal review Update to version 1.14.6: * Test: populating build test failure * fix(auto): keep first matching zone file for duplicate origins * plugin/secondary: serve catalog member zones * plugin/tsig: don't echo client's TSIG.Error if verification is successful * docs(timeouts): document DoQ read timeout * plugin/dnstap: fix self-deadlock in listener broadcast on client flush error * core/dnsserver: bound DoQ stream read with the server read timeout * plugin/transfer: Fix panic in CoreDNS transfer plugin caused by empty DNS record * core/dnsserver: add Config.UDPDecorateWriterFunc for external plugins * plugin/kubernetes: fix AXFR panic when nsAddrs returns multiple records * plugin/hosts: fix data race between lookups and reload * core/dnsserver: sanitize DoH/DoH3 request parse errors * plugin/dnstap: close the previous connection before reconnecting * plugin/erratic: apply default truncate amount of 2 for bare * Test: Fix flaky health test * plugin/pkg/response: classify nxdomain without soa as denial * plugin/file: return SOA in authority for negative CNAME target answers * plugin/forward: make per-upstream read timeout configurable * plugin/secondary: parse catalog zones after transfer * plugin/pkg/dnsutil: guard Join against an empty label slice * plugin/file: run additional processing for wildcard answers * fix(tls): use Go TLS defaults * plugin/secondary: stop update loop on reload shutdown * fix(8201): restore old behavior forward plugin continue on empty conf file * fix(forward): make dnstap FORWARDER_* describe the socket from CoreDNS to upstream * plugin/cache: add regression test for AD bi
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- openSUSE:Leap 16.0 coredns0 → 1.14.7-bp160.2.1
How to fix openSUSE-SU-2026:22135-1
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for openSUSE-SU-2026:22135-1. A missing EPSS score is not a low risk. Compare Security update for coredns with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 1.14.7-bp160.2.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 19, 2026 · OpenSSF OSV / OSV Scanner
Detected
This update for coredns fixes the following issues: Changes in coredns: - Bump vendored google.golang.org/grpc from 1.83.0 to 1.83.1: * CVE-2026-84304: heap memory exhaustion via HTTP/2 DATA frame fragmentation in the gRPC transport (boo#1279216) * Done through the go_modules "require" parameter in _service - Update license tag to Apache-2.0 AND MPL-2.0 * outcome of legal review Update to version
Oct 20, 2026 · OpenSSF OSV / OSV Scanner
Fix available
coredns fixed in 1.14.7-bp160.2.1
Oct 20, 2026 · OpenSSF OSV / OSV Scanner
Fix available
coredns fixed in 1.14.7-bp160.2.1
Oct 20, 2026 · OpenSSF OSV / OSV Scanner
Updated
This update for coredns fixes the following issues: Changes in coredns: - Bump vendored google.golang.org/grpc from 1.83.0 to 1.83.1: * CVE-2026-84304: heap memory exhaustion via HTTP/2 DATA frame fragmentation in the gRPC transport (boo#1279216) * Done through the go_modules "require" parameter in _service - Update license tag to Apache-2.0 AND MPL-2.0 * outcome of legal review Update to version
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryopenSUSE-SU-2026:22135-1
Security update for coredns
osv.dev
References
Freshness
Last verified in this catalog Oct 20, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.