Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-4891: Heap Out-of-Bounds Read in dnsmasq DNSSEC RRSIG Validation

Published May 11, 2026 · Updated 6 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 4 in a dayToday
CVSS7.5High · v3.1
EPSS6.4%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Thekelleys
IdentifiersCVE-2026-4891CWE-125 · Out-of-bounds Read

CVE-2026-4891 is a heap-based out-of-bounds read vulnerability in dnsmasq DNSSEC validation. An underflow involving the RRSIG record length (rdlen) causes validation to read beyond a heap buffer when processing a crafted DNS packet. A remote attacker can trigger the flaw to cause denial of service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disrupt dnsmasq availability and DNS resolution for dependent clients. Information disclosure, arbitrary code execution, and integrity compromise are not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Until patched packages can be deployed, limit exposure of dnsmasq DNS services to untrusted networks and restrict which systems can send DNS responses or packets to the resolver. Monitor for dnsmasq crashes and anomalous malformed DNS traffic.

Remediation

Patch, then assume compromise.

Install the vendor-provided dnsmasq security update for the applicable product stream. Corrected Red Hat package releases include 2.79-21.el8_6.6 for RHEL 8.6, 2.79-26.el8_8.5 for RHEL 8.8, 2.79-36.el8_10 for RHEL 8.10, 2.85-6.el9_2.5 for RHEL 9.2, 2.85-16.el9_4.1 for RHEL 9.4, 2.85-17.el9_6.1 for RHEL 9.6, 2.85-18.el9_8.1 for RHEL 9.8, 2.90-4.el10_0.1 for RHEL 10.0, and 2.90-7.el10_2 for RHEL 10.2. Use the corresponding corrected release or a newer vendor-supported update within the applicable stream. OpenShift Container Platform 4.19 deployments should apply release 4.19.39 or a subsequent corrected release through their release channel.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
dnsmasq-cve-2026This repository is a dnsmasq vulnerability verification toolkit centered on CVE-2026-2291, CVE-2026-5172, CVE-2026-4890, CVE-2026-4891, CVE-2026-4892, and CVE-2026-4893. It is not tied to a common exploit framework. The repository contains four functional scripts plus documentation: (1) dnsmasq_cve_verify.py is the primary end-to-end black-box verifier that runs from a testing laptop, starts a malicious DNS service, sends trigger traffic to the DUT, and uses SSH to inspect dnsmasq state and logs before issuing PASS/FAIL verdicts; (2) malicious_dns_server.py is a standalone UDP DNS server that returns crafted malformed responses for manual reproduction of selected parser bugs, notably CVE-2026-5172 and DNSSEC-related issues; (3) test_dnsmasq_cve_remote.py is a lightweight remote detection script that queries version.bind over UDP/53 and infers vulnerability status from the reported dnsmasq version; and (4) test_dnsmasq_cve_on_device.sh is a shell-based local checker that runs on the target device and uses version/strings heuristics to assess patch status and feature applicability. The main exploit capability is network-based triggering of dnsmasq parsing flaws through malicious DNS responses. The code crafts malformed CNAME/rdlen combinations, DNSSEC/NSEC/RRSIG-related records, and ECS-related inputs to induce crashes, hangs, or logic bypasses in vulnerable dnsmasq builds. The README also describes a DHCPv6 CLID overflow test for CVE-2026-4892, which is a local/adjacent vector requiring DHCPv6 support and dhcp-script configuration. The repository therefore mixes active exploit-style verification with auxiliary detection scripts. Because payloads are hardcoded and purpose-built for QA verification rather than generalized post-exploitation, the maturity is best classified as OPERATIONAL rather than weaponized. Fingerprintable observables include the default DUT IP 192.168.1.1, example attacker IP 10.0.0.211, SSH on TCP/22, DNS on UDP/53, trigger domains such as crash-5172.evil.test and crash-2291.evil.test, the version.bind CHAOS TXT query, and DUT file paths like /etc/dnsmasq.conf, /tmp/resolv.conf.auto, /sbin/dnsmasq, /usr/sbin/dnsmasq, and /var/log/messages*. Overall, the repository’s purpose is QA/security validation of dnsmasq patch status and exploitability in live devices, especially routers or embedded Linux systems using dnsmasq as a DNS forwarder.JianrongXiao-Linksys · Disclosed Jun 1, 2026 · python · bash · network · local · wirelessOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ThekelleysDnsmasqapplication
FAQ

Frequently asked questions

Is CVE-2026-4891 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-4891 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-4891?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-4891, the earliest disclosed Jun 1, 2026.
Is there a patch for CVE-2026-4891?
Install the vendor-provided dnsmasq security update for the applicable product stream. Corrected Red Hat package releases include 2.79-21.el8_6.6 for RHEL 8.6, 2.79-26.el8_8.5 for RHEL 8.8, 2.79-36.el8_10 for RHEL 8.10, 2.85-6.el9_2.5 for RHEL 9.2, 2.85-16.el9_4.1 for RHEL 9.4, 2.85-17.el9_6.1 for RHEL 9.6, 2.85-18.el9_8.1 for RHEL 9.8, 2.90-4.el10_0.1 for RHEL 10.0, and 2.90-7.el10_2 for RHEL 10.2.
What products are affected by CVE-2026-4891?
Thekelleys Dnsmasq.
How severe is CVE-2026-4891?
CVE-2026-4891 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 6.4% (94th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+23 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.