CVE-2026-93006VulnerabilityPublished 29 Oct 2026

CWE-672

Source GCVE Database

Compare

Authoritative record:CVE-2026-93006· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium.

Data as of 29 Oct 2026, 16:54 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	6.8

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-fp59-6rfj-9jgw

What to do

Affected software

Product	Affected	Fixed in
Red Hat Ceph Storage 9rhceph/alloy-rhel10	Affected–	Fixed in–
Red Hat Enterprise Linux 10dnsmasq	Affected–	Fixed in–
Red Hat Enterprise Linux 6dnsmasq	Affected–	Fixed in–
Red Hat Enterprise Linux 7dnsmasq	Affected–	Fixed in–
Red Hat Enterprise Linux 8dnsmasq	Affected–	Fixed in–
Red Hat Enterprise Linux 9dnsmasq	Affected–	Fixed in–

AI-suggested

Red Hat advises the following mitigations: 1) Disable TFTP if it is not required by removing the --enable-tftp option from dnsmasq configuration. 2) If TFTP is needed, restrict it to specific interfaces using --tftp-interface=<interface> and avoid running TFTP-only instances serving untrusted clients on the same network. 3) Compile dnsmasq without TFTP support using COPTS=-DNO_TFTP if TFTP functionality is unnecessary. Users should verify their dnsmasq version and configuration accordingly.

Description

A vulnerability in dnsmasq's TFTP server allows serving incorrect file contents due to a stale transfer cache not being invalidated after a transfer completes. This can cause a client to receive previously cached data instead of the requested file. In PXE network-boot environments, this flaw can enable an attacker on the local network to substitute attacker-chosen boot content for a victim machine. The attack complexity is high and the attack vector is limited to adjacent networks. Mitigations include disabling TFTP if not needed, restricting TFTP interfaces, or compiling dnsmasq without TFTP support.

Impact

The vulnerability can lead to clients receiving incorrect TFTP file contents, potentially allowing an attacker on the local network to substitute malicious PXE boot content for victims. This impacts confidentiality and integrity of the boot process but does not affect availability. The attack vector is limited to adjacent networks and requires high complexity, including heap reuse and DNS cache key manipulation. Mixed DNS/TFTP environments reduce exploitability, while TFTP-only PXE servers without DNS are at highest risk.

Summary

CVE-2026-93006 is a vulnerability in dnsmasq where the TFTP server's transfer cache is not invalidated upon transfer completion, causing it to serve stale file contents to subsequent clients. This flaw allows an attacker on the local network who can request TFTP files to cause later clients to receive cached data from previous transfers. In PXE network-boot environments, this can lead to substitution of attacker-controlled boot content, impacting confidentiality and integrity. The attack requires adjacent network access and has high complexity due to factors like DNS forwarding overwriting the TFTP cache key and heap reuse requirements. Mixed DNS/TFTP deployments are harder to exploit, with TFTP-only PXE servers without DNS being the highest risk. Red Hat's dnsmasq packages at version 2.90 or earlier do not contain the vulnerable TFTP prefetch cache introduced in version 2.92. Products shipping dnsmasq 2.92 or newer with TFTP enabled at runtime may be affected. Red Hat rates this vulnerability as Important with a CVSS 3.1 score of 6.8.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 16:54 UTC

WeaknessesCWE-672

Technical details

References

Community reviews

Related threats