Quick answers
- Is CVE-2026-93010 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93010 being exploited in the wild.
- How severe is CVE-2026-93010?
- Medium severity, with a CVSS score of 4.3, published 29 October 2026.
- Which products and versions are affected?
- Dnsmasq 2.92 and later.
- Is there a fix for CVE-2026-93010?
- No fixed version is recorded yet. Use --leasequery=<addr>[/prefix] to restrict queries to designated relays; disable the leasequery feature if not needed (it is off by default); or use firewall rules to limit which hosts can send DHCP packets to dnsmasq. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93010 attacked?
- It is attacked from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-93010?
- Check whether you run Dnsmasq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Use --leasequery=<addr>[/prefix] to restrict queries to designated relays; disable the leasequery feature if not needed (it is off by default); or use firewall rules to limit which hosts can send DHCP packets to dnsmasq.
Technical details
A missing authorization flaw in dnsmasq's DHCP leasequery feature (available in v2.92+) allows unauthenticated queries from any source on the adjacent network when the feature is enabled without specifying allowed source addresses. An attacker with network access can query the DHCP server to enumerate lease records and discover network topology and device information. The vulnerability is CWE-862 (missing authorization) and requires the administrator to have explicitly enabled the --leasequery flag without address restrictions.
Affected products
- dnsmasq dnsmasq 2.92 and later
Timeline
- 2026-10-29: disclosed