Servers and applications
CVE-2026-11331
An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through…
- Severity
- High 7.5
- Published
- 22 Jul 2026
- Last changed
- 2 Nov 2026
- Added to UpHeron
- 2 Nov 2026
- Exploit chance
- 0.4% in the next 30 daysHigher than 37% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-790
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Sources
- NVD
Description
An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Affected software
| Software | Affected versions |
|---|---|
BIND 9Servers and applications · cpe:a:isc:bind |
|
About BIND 9
DNS server software
- Developer
- Internet Systems ConsortiumWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- CWikidata
- First released
- 1984Wikidata
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 9.21 (Development) | 9.21.27 | Yes |
| 9.20 (Stable) (LTS)LTS | 9.20.30 | Until 8 Jul 2028 |
| 9.18 (ESV) (LTS)LTS | 9.18.50 | Ended 30 Jun 2026 |
| 9.16 (LTS)LTS | 9.16.50 | Ended 31 Mar 2024 |
From endoflife.date.
Vulnerabilities in BIND 9
- In our list
- 197
- Published in the last 12 months
- 23
- Critical, last 12 months
- 1
- High, last 12 months
- 15
- Known exploited
- 1
- CVE-2026-97313Specific RPZ configurations and query patterns may result in an unexpected exitHigh 7.5 21 Oct 2026
- CVE-2026-96888Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimizationHigh 7.5 21 Oct 2026
- CVE-2026-94300Concurrent GSS-TSIG messages corrupt memoryHigh 8.1 21 Oct 2026
- CVE-2026-19630Amplified resource exhaustion in inbound message processingHigh 7.5 21 Oct 2026
- CVE-2026-13321The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.High 8.6 22 Jul 2026
- CVE-2026-13204If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.High 7.5 22 Jul 2026