CVE-2026-5947
Undefined behavior may result due to a race condition leading to a …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- downloads.isc.org/isc/bind9/9.20.23
- downloads.isc.org/isc/bind9/9.21.22
- kb.isc.org/docs/cve-2026-5947
- access.redhat.com/errata/RHSA-2026:7412
- access.redhat.com/security/cve/CVE-2026-5947
- bugzilla.redhat.com/show_bug.cgi?id=2479772
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5947.json
- nvd.nist.gov/vuln/detail/CVE-2026-5947
- cve.org/CVERecord?id=CVE-2026-5947
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.