Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.

BIND DNS Server Consumes Excessive CPU When Processing Malicious Zone

published 6 months ago
Summary

A security update is available for the BIND DNS server that prevents it from using too much CPU when processing maliciously crafted DNS data. This update affects some versions of the BIND software and is important for organizations that rely on DNS for their online presence. To stay secure, update to the latest version of BIND as soon as possible.

What to do
  • Update openeuler bind to version 9.16.23-29.oe2203sp4.
Affected software
Ecosystem VendorProductAffected versions
openEuler:22.03-LTS-SP4 openeuler bind < 9.16.23-29.oe2203sp4
Fix: upgrade to 9.16.23-29.oe2203sp4
Original advisory text
bind security update
BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly.

Security Fix(es):

If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU. Authoritative-only servers are generally unaffected, although there are circumstances where authoritative servers may make recursive queries (see: https://kb.isc.org/docs/why-does-my-authoritative-server-make-recursive-queries).
This issue affects BIND 9 versions 9.11.0 through 9.16.50, 9.18.0 through 9.18.46, 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.46-S1, and 9.20.9-S1 through 9.20.20-S1.(CVE-2026-1519)
Timeline
Published25 Apr 2026
Updated25 Apr 2026
First seen25 Apr 2026
Sources
Track software like this
Free during beta