Skip to main content
Mallory
← Back to News
proof-of-concept-releaseembedded-device-vulnerabilityinternet-facing-service-vulnerabilitywidely-deployed-product-advisory

Dnsmasq Heap Overflow Enables DNS Cache Poisoning and Potential Remote Code Execution

Patch & Detection Intelligence · 2 sources · Updated 4mo ago · First seen Jul 20, 2026

Dnsmasq Heap Overflow Enables DNS Cache Poisoning and Potential Remote Code Execution

A heap buffer overflow in Dnsmasq tracked as CVE-2026-2291 can be triggered when the resolver processes malicious DNS replies from an upstream DNS server, allowing memory corruption, false cache entry injection, DNS redirection, and denial of service. The flaw affects code introduced in release 2.73 and is tied to unsafe strcpy() use during cache insertion after extract_name() converts DNS names from wire format into C strings, where escaped names can exceed the 1,025-byte bigname heap buffer.

Researchers reported practical exploitation against OpenWRT 24.10.4 configured to use a malicious upstream resolver, using crafted requests and CNAME chains to corrupt the bigname free list, obtain a write-what-where primitive, and overwrite a function pointer in musl ld.so to gain instruction-pointer control. The issue was fixed on 11 May 2026 in versions 2.92rel2 and 2.93, and public reporting warns that exposed deployments could face DNS hijacking or, under the demonstrated conditions, full remote code execution.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

4 events · May 11, 2026 – Jul 20, 2026
  1. Jul 20, 20264mo ago

    oss-sec post highlights exploitation impacts of CVE-2026-2291

    An oss-sec mailing list post described CVE-2026-2291 as enabling heap buffer overflow exploitation that could inject false DNS cache entries, redirect DNS queries to attacker-controlled IP addresses, or cause denial of service. The post also referenced Exodus Intelligence's separate RCE analysis.

    oss-sec: Re: dnsmasq vulnerabilities, including attacker DNS redirect, privilege escalation, and heap manipulation
  2. Jul 20, 20264mo ago

    Exodus Intelligence publishes technical analysis and RCE demonstration

    Exodus Intelligence published technical details for CVE-2026-2291, showing how the bug can overflow the bigname heap buffer and be exploited. The analysis demonstrated practical remote code execution against an OpenWRT 24.10.4 target configured to use a malicious upstream DNS server.

    Dnsmasq DNS Remote Heap Buffer Overflow - Exodus Intelligence
  3. Jul 20, 20264mo ago

    Dnsmasq 2.73 introduces the vulnerable code path

    The vulnerable heap buffer overflow condition tied to CVE-2026-2291 was introduced in Dnsmasq release 2.73, in the cache insertion path using unsafe strcpy() handling of expanded DNS names.

    Dnsmasq DNS Remote Heap Buffer Overflow - Exodus Intelligence
  4. May 11, 20266mo ago

    Dnsmasq fixes CVE-2026-2291 in versions 2.92rel2 and 2.93

    On 2026-05-11, the heap buffer overflow vulnerability CVE-2026-2291 was fixed in Dnsmasq versions 2.92rel2 and 2.93. The flaw could be triggered while processing malicious DNS replies from an upstream DNS server.

    Dnsmasq DNS Remote Heap Buffer Overflow - Exodus Intelligence
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Affected products

1 linked
Dnsmasq

Observables

3 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.