Live › vulnerability › CVE-2026-93006
dnsmasq's built-in TFTP server keeps a recently used transfer cache that is not cleared when a transfer finishes, so a later client can receive previously cached file contents instead of the file it asked for. In PXE network-boot setups an attacker on the local network may be able to substitute boot content on a victim machine.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 13:25 UTC. All times on this page are UTC.
Only systems running dnsmasq with its TFTP server enabled are exposed, typically PXE network-boot environments that serve boot files on the local network. Hosts that do not enable TFTP in dnsmasq are not affected by this flaw. The sources do not list affected versions or a fixed release.
No product ranges from the sources yet.
enable-tftp in the dnsmasq configuration (/etc/dnsmasq.conf or files under /etc/dnsmasq.d/).dnsmasq --version.No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-93006")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.