How severe is CVE-2026-5947?

CVE-2026-5947 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-5947 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-5947?

CVE-2026-5947 affects Isc Bind. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-5947?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-5947 have an EU (EUVD) identifier?

Yes. CVE-2026-5947 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-31110.

When was CVE-2026-5947 published?

CVE-2026-5947 was published on 2026-05-20 and last updated on 2026-06-30.

CVE-2026-5947

CVE-2026-5947 is a high-severity vulnerability in Isc Bind with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (69th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-31110
Weakness: CWE-362
Affected product: Isc Bind
Published: 2026-05-20
Last modified: 2026-06-30

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2026-5947?: CVE-2026-5947 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-5947 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (69th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-5947?: CVE-2026-5947 affects Isc Bind. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-5947?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-5947 have an EU (EUVD) identifier?: Yes. CVE-2026-5947 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-31110.
When was CVE-2026-5947 published?: CVE-2026-5947 was published on 2026-05-20 and last updated on 2026-06-30.

References

Affected products (1)

cpe:2.3:a:isc:bind:*:*:*:*:-:*:*:*

More vulnerabilities in Isc Bind

CVE-2008-0122 — Critical (CVSS 10.0): Off-by-one error in the inet_network function in libbind in ISC BIND 9.4.2 and earlier, as used in libc in FreeBSD 6.2…
CVE-2001-0011 — Critical (CVSS 10.0): Buffer overflow in nslookupComplain function in BIND 4 allows remote attackers to gain root privileges.
CVE-2001-0013 — Critical (CVSS 10.0): Format string vulnerability in nslookupComplain function in BIND 4 allows remote attackers to gain root privileges.
CVE-2001-0010 — Critical (CVSS 10.0): Buffer overflow in transaction signature (TSIG) handling code in BIND 8 allows remote attackers to gain root privileges.
CVE-2000-1029 — Critical (CVSS 10.0): Buffer overflow in host command allows a remote attacker to execute arbitrary commands via a long response to an AXFR…
CVE-1999-0837 — Critical (CVSS 10.0): Denial of service in BIND by improperly closing TCP sessions via so_linger.

All CVEs affecting Isc Bind →

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →