CVE-2026-93008

Dnsmasq: dnsmasq: out-of-bailiwick cache injection through cname chase in split-dns configurations

  • Medium 6.8

Description

A flaw was found in dnsmasq. When following a CNAME in a DNS response, the resolver can cache records for the CNAME target without checking that those records belong to the responding server's authorized zone. In split-DNS deployments that send some domains to a specific upstream, an attacker who controls that upstream can inject cache entries for unrelated names. Later clients may then receive attacker-chosen addresses for those names.

Key facts

Published
29 Oct 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.15% likely to be exploited in the next 30 days, higher than 4.196% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.8CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

What to do

  • The following measures reduce risk: 1. Do not point server=/domain/ at untrusted or attacker-reachable DNS servers. 2. Restrict dnsmasq to communicate only with trusted upstream resolvers at the firewall. 3. For local=/domain/ zones, define all names that should be served locally. 4. Do not rely on --dnssec to mitigate this for unsigned zones. Insecure records are still cached.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ceph Storage 9
  • Default status: affected
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: affected
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected
Red HatRed Hat OpenStack Platform 13 (Queens)
  • Default status: affected
Red HatRed Hat OpenStack Platform 18.0
  • Default status: affected

Timeline

  1. 14 Sep 2026 Reported to Red Hat.
  2. 28 Oct 2026 Made public.
  3. 29 Oct 2026 Published

Weakness

References