CVE-2026-4890: High severity Dnsmasq Dnsmasq vulnerability

Published Apr 14, 2026
·
Updated

A Denial of Service (DoS) vulnerability in the DNSSEC validation of dnsmasq allows remote attackers to cause a denial of service via a crafted DNS packet.

Other sources

NSEC/NSEC3 bitmap window iteration in dnssec.c advances by p[1] instead of p[1] + 2, missing the 2-byte window header. When bitmaplength=0, neither rdlen nor p change, creating an infinite loop. Two instances at dnssec.c:1290 and dnssec.c:1450. Reachable before RRSIG validation so no valid signatures are needed. One of the two sites was coincidentally fixed in 2.92. Fix: add +2 to both the pointer advance and rdlen decrement.

Red Hat

Affected Software

4 affected componentsFixes available
Dnsmasq Dnsmasq
debian/dnsmasq<=2.85-1, <=2.85-1+deb11u1, <=2.92-4
2.90-4~deb12u22.91-1+deb13u12.92-5
Microsoft azl3 dnsmasq 2.90-1
Microsoft azl3 dnsmasq 2.92-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/dnsmasq to a version that resolves this vulnerability.

    Fixed in 2.90-4~deb12u2Fixed in 2.91-1+deb13u1Fixed in 2.92-5
  2. Upgrade

    Upgrade dnsmasq to a version that resolves this vulnerability.

    Fixed in 2.92
  3. Configuration

    In dnssec.c at the two instances (dnssec.c:1290 and dnssec.c:1450), adjust NSEC/NSEC3 bitmap window iteration so it advances by p[1] + 2 (not p[1]) and decrements rdlen by the corresponding amount (add +2 to both operations) to account for the missing 2-byte window header.

    dnssec.c (dnsmasq DNSSEC validation) pointer advance and rdlen decrement in NSEC/NSEC3 bitmap window iteration = +2 to both the pointer advance and rdlen decrement
  4. Compensating control

    Add/ensure a guard in dnssec.c so that when bitmap_length=0, the loop terminates (avoid the infinite loop where neither rdlen nor p change).

Event History

Apr 14, 2026
Data Sourced
via Red Hat·10:39 PM
DescriptionSeverityAffected Software
May 11, 2026
CVE Published
via MITRE·04:47 PM
Data Sourced
via MITRE·04:47 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverity
Data Sourced
via NVD·06:16 PM
Weakness
May 13, 2026
Data Sourced
via Ubuntu·03:07 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·03:08 PM
Description
May 15, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Updated
via Microsoft·08:02 AM
Affected Software
May 16, 2026
Data Sourced
via Debian·03:10 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-4890?

CVE-2026-4890 is classified as a Denial of Service (DoS) vulnerability that can disrupt DNS services.

2

How do I fix CVE-2026-4890?

To fix CVE-2026-4890, update dnsmasq to version 2.90-4~deb12u2, 2.91-1+deb13u1, or 2.92-5.

3

Which versions of dnsmasq are affected by CVE-2026-4890?

CVE-2026-4890 affects dnsmasq versions up to and including 2.85-1, 2.85-1+deb11u1, 2.90-4~deb12u1, 2.91-1, and 2.92-4.

4

Can CVE-2026-4890 be exploited remotely?

Yes, CVE-2026-4890 can be exploited by remote attackers through a crafted DNS packet.

5

What impact does CVE-2026-4890 have on systems?

CVE-2026-4890 can lead to a denial of service, rendering DNS resolution unavailable for affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203