DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

Concurrent GSS-TSIG messages corrupt memory

Windows service and uninstall paths are not quoted when BIND is installed

Specific RPZ configurations and query patterns may result in an unexpected exit

Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization

Amplified resource exhaustion in inbound message processing

Validating resolver can abort while caching a mismatched NOQNAME proof

named aborts on a TKEY query when the user configuration has no global options statement

Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path

SVCB AliasMode additional-data error leaks qpcache references

Unauthenticated remote crash of named via a single DoH SIG(0) request

Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`

Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees

Unexpected exit in certain situations with NSEC and NSEC3 both present

Record ordering based unexpected exit with CNAME or DNAME

Cache poisoning possible with label count discrepancy, RRSIG, and wildcards

Potential memory usage beyond configured limits

Unnecessary validation of DNSSEC signed records

Potential wildcard CNAME RPZ policy bypass

Invalid handling of CLASS != IN

BIND 9 server memory exhaustion during GSS-API TKEY negotiation

Memory leak in code preparing DNSSEC proofs of non-existence

Excessive NSEC3 iterations cause high CPU load during insecure delegation validation

Malformed BRID/HHIT records can cause named to terminate unexpectedly

A malformed request can trigger an assertion failure in badcache.c

Improper fetch cleanup sequencing in the resolver can cause named to crash

A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

A flaw in the "deny-answer-aliases" feature can cause an assertion failure in named

Some versions of BIND can improperly permit recursive query service to unauthorized clients

BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is not enabled.