Cache poisoning attacks with unsolicited RRs
Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache.
Red Hat Hardened Images RPMs bug fix and enhancement update
Released 2026-04-07 · Red Hat rating Important · View on Red Hat →
Under certain circumstances, BIND is too lenient when accepting records from answers, allowing an attacker to inject forged data into the cache.
Querying for records within a specially crafted zone containing certain malformed DNSKEY records can lead to CPU exhaustion.
Malformed BRID/HHIT records can cause `named` to terminate unexpectedly.
In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use.
If a BIND resolver is performing DNSSEC validation and encounters a maliciously crafted zone, the resolver may consume excessive CPU.
A specially crafted domain can be used to cause a memory leak in a BIND resolver simply by querying this domain.
Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record.
A use-after-return vulnerability exists in the `named` server when handling DNS queries signed with SIG(0).