Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-4893: ECS Source-Validation Bypass in dnsmasq

Published May 11, 2026 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days14 mentions · peak 4 in a dayToday
CVSS5.3Medium · v3.1
EPSS1.8%79th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Thekelleys
IdentifiersCVE-2026-4893CWE-20

CVE-2026-4893 is an information disclosure vulnerability in dnsmasq involving incorrect validation of EDNS Client Subnet (ECS) information defined by RFC 7871. A remote attacker can use a crafted DNS packet containing client subnet information to bypass source checks. The affected function, precise validation error, and upstream affected-version range are not specified.

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 bypasses dnsmasq source validation and can disclose information to a remote attacker. The specific information exposed and the extent of the confidentiality impact are not established. Code execution, integrity compromise, and denial of service are not established for this vulnerability.

Mitigation

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

Until patches are deployed, restrict exposure of dnsmasq resolver services to trusted networks and limit acceptance of DNS responses to expected upstream resolver paths. Products with management or network-service access controls should restrict those interfaces to trusted administrators and networks.

Remediation

Patch, then assume compromise.

Install the vendor-provided dnsmasq security update for the applicable product and support stream. Corrected Red Hat package builds 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 these builds or their vendor-designated successors within the corresponding stream. For RHEL 7, apply RHSA-2026:99723. Update affected EulerOS Virtualization installations according to EulerOS-SA-2026-4632 or EulerOS-SA-2026-4690. Affected OpenShift Container Platform 4.19 deployments should upgrade to 4.19.39 or a superseding fixed release through the appropriate release channel.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE20264893pocThis repository is a small, focused proof-of-concept exploit for a dnsmasq ECS validation issue. It contains three files: a Python exploit script (exp.py), a sample dnsmasq configuration (dnsmasq.conf), and a short README with setup steps. The exploit is not part of a larger framework. The main logic is in exp.py. It implements a fake upstream UDP DNS server that binds to 127.0.0.1:5354, which matches the upstream server configured in dnsmasq.conf. The script parses incoming DNS queries, only responds if the source IP is 127.0.0.1 (dnsmasq) and the queried name is trigger.evil.com., then sends back a crafted DNS response containing: (1) an A record resolving the trigger name to 1.2.3.4, and (2) an EDNS0 ECS option (code 8) with a deliberately mismatched subnet value of 127.18.0.0/24. The intended capability is to demonstrate that a vulnerable dnsmasq instance improperly accepts this mismatched ECS response from its upstream server. The script also includes a built-in self-test thread. After startup, it sends a DNS query for trigger.evil.com to the configured dnsmasq listener at xxx.xxx.xxx.x:5353, waits for dnsmasq's reply, parses the answer section, and reports the target as vulnerable if dnsmasq returns the fake IP 1.2.3.4. This makes the repository both an exploit PoC and a validation harness. Repository structure and purpose: - exp.py: primary exploit and verification logic; contains DNS packet parsing, DNS response crafting, ECS option construction, UDP listener, and self-test. - dnsmasq.conf: minimal sample configuration showing dnsmasq listening on port 5353 and forwarding to 127.0.0.1:5354. - readme.txt: setup instructions, including enabling add-subnet and running the Python script. Overall, this is an operational network-based PoC for testing whether dnsmasq accepts attacker-controlled upstream DNS replies with mismatched ECS metadata. It does not deliver code execution; instead, it demonstrates DNS response spoofing/poisoning-style behavior by causing dnsmasq to return an attacker-chosen IP for a controlled domain under specific configuration conditions.lottiedeyan · Disclosed May 27, 2026 · python · text · networkOperationaldnsmasq-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-4893 exploited in the wild?
As of Nov 13, 2026, Mallory has no reports of CVE-2026-4893 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-4893?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-4893, the earliest disclosed May 27, 2026.
Is there a patch for CVE-2026-4893?
Install the vendor-provided dnsmasq security update for the applicable product and support stream. Corrected Red Hat package builds 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-4893?
Thekelleys Dnsmasq.
How severe is CVE-2026-4893?
CVE-2026-4893 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 1.8% (79th percentile) as of Nov 13, 2026.
Activity feed

Recent activity

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

View more in app →
+28 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.