CVE-2026-93006

Dnsmasq: dnsmasq: tftp prefetch cache keyed on stale heap pointer serves wrong file content

  • Medium 6.8

Description

A flaw was found in dnsmasq. The TFTP server can serve the wrong file contents because a recently used transfer cache is not invalidated when a transfer finishes. An attacker on the local network who can request a TFTP file may cause a later client to receive previously cached data instead of the requested file. In PXE network-boot environments this can substitute attacker-chosen boot content for a victim machine.

Key facts

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

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:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • The following measures reduce risk: 1. If TFTP is not required, do not enable it. Remove --enable-tftp from the dnsmasq configuration. 2. If TFTP is required, restrict it with --tftp-interface=<interface> and avoid running TFTP-only instances that serve untrusted clients on the same network. 3. Compile without TFTP support using COPTS=-DNO_TFTP if TFTP is not needed.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