Uncaught Exception Affecting kubernetes-dns-node-cache-fips package, versions <1.26.8-r8


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.46% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-KUBERNETESDNSNODECACHEFIPS-21177993
  • published18 Oct 2026
  • disclosed16 Jul 2026

Introduced: 16 Jul 2026

CVE-2026-62994  (opens in a new tab)
CWE-248  (opens in a new tab)
CWE-755  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kubernetes-dns-node-cache-fips to version 1.26.8-r8 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubernetes-dns-node-cache-fips package and not the kubernetes-dns-node-cache-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

CoreDNS is a DNS server written in Go. From 1.9.4 until 1.14.5, a network DNS client allowed to request AXFR for a CoreDNS zone can trigger a panic when CoreDNS is configured with k8s_external headless-service zone transfers and Kubernetes contains a headless service endpoint with no declared ports; plugin/kubernetes/object/endpoint.go creates Port: -1, plugin/k8s_external/msg_to_dns.go skips that service, plugin/k8s_external/transfer.go sends an empty []dns.RR batch, and plugin/transfer/transfer.go indexes records[0] without checking the batch is non-empty. This issue is fixed in version 1.14.5.

CVSS Base Scores

version 3.1