Servers and applications
CVE-2026-5947
Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the "recursive-clients" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while…
- Severity
- Medium 5.9
- Published
- 20 May 2026
- Last changed
- 24 Aug 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 9.20.23, 9.21.22
- Exploit chance
- 1.4% in the next 30 daysHigher than 72% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Race condition (CWE-362)Use after free (CWE-416)Time-of-check time-of-use race condition (CWE-367)
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H- Sources
- NVD
Description
Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the "recursive-clients" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.
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