VulnerabilityPublished 29 Oct 2026

CVE-2026-93007: Uncontrolled Resource Consumption

Source GCVE Database

Compare

Authoritative record:CVE-2026-93007· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 16:54 UTC

CVSS 3.1 base score

5.3Medium

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	5.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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-2frf-fr59-fcjq

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

Administrators should increase the TCP connection limit using the --max-tcp-connections option to raise the number of connections required to exhaust the pool. Additionally, firewall rules should be applied to limit the number of TCP connections per source IP to port 53, for example using iptables connlimit. Restricting access to TCP port 53 from untrusted networks is also recommended if TCP DNS is not required.

Description

A vulnerability in dnsmasq's TCP DNS service allows remote attackers to exhaust a fixed pool of child processes by opening idle TCP connections to port 53. This prevents new TCP DNS connections and disrupts DNSSEC validation that requires TCP fallback. UDP DNS resolution remains unaffected, and the occupied slots are released after a fixed timeout. The impact is limited to TCP-dependent DNS operations, and the condition auto-recovers unless the attacker maintains connections.

Impact

The vulnerability causes a denial of service condition for TCP DNS connections, affecting DNSSEC validation and other TCP-dependent DNS operations. UDP DNS resolution is not impacted. The denial of service is temporary, as occupied child process slots are released after approximately 150 seconds, but can be sustained by repeated attacker connections. The overall availability impact is low, with no confidentiality or integrity impact.

Summary

The dnsmasq TCP DNS service uses a small fixed pool of child processes without a receive timeout on client connections. An attacker can open idle TCP connections to port 53 to occupy all child process slots, causing denial of service for new TCP DNS connections and DNSSEC validation relying on TCP fallback. UDP DNS queries continue to function normally, and occupied slots are freed after a fixed lifetime. The vulnerability affects Red Hat products shipping dnsmasq as a DNS forwarder. Mitigations include increasing the maximum TCP connection limit and applying firewall rules to limit per-source TCP connections to port 53.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats