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.
No advisories yet.
Solution
Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.23, 9.21.22, or 9.20.23-S1.
Workaround
No workarounds known.
Wed, 20 May 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 20 May 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | SIG(0) validation during query flood may lead to undefined behavior | |
| First Time appeared |
Isc
Isc bind |
|
| Weaknesses | CWE-362 CWE-416 |
|
| CPEs | cpe:2.3:a:isc:bind:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Isc
Isc bind |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: isc
Published:
Updated: 2026-05-20T13:39:38.654Z
Reserved: 2026-04-09T06:40:58.672Z
Link: CVE-2026-5947
Updated: 2026-05-20T13:39:19.676Z
Status : Awaiting Analysis
Published: 2026-05-20T13:16:40.303
Modified: 2026-05-20T14:04:57.320
Link: CVE-2026-5947
No data.
OpenCVE Enrichment
Updated: 2026-05-20T14:45:32Z