Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-5947Published 2026-05-20

CVE-2026-5947 — ISC BIND 9

high

As of 2026-05-20, CVE-2026-5947 is a HIGH-severity vulnerability in ISC BIND 9, CVSS v3.1 7.5, EPSS 0.0% (13.7th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-5947, most recently “BIND 9 Multi-CVE Disclosure (May 2026) — Heap UAF in DoH (CVE-2026-3593), SIG(0) UAF (CVE-2026-5947), Resolver Resend Loop DoS (CVE-2026-5950), CLASS!=IN Assertion DoS (CVE-2026-5946), Glue Amplification (CVE-2026-3592), GSS-API TKEY Memory Exhaustion (CVE-2026-3039)”.

CVSS v3.1
7.5/10High
EPSS
0.0%Higher than 13.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
4.3/10Threadlinqs triage score
Published
CVSS v3.1 7.5 (HIGH) · EPSS 0.0% (higher than 13.7% of all scored CVEs) · Priority 4.3/10 · Published 2026-05-20

Last updated:

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.

The record classifies CVE-2026-5947 under weakness classes CWE-362, CWE-416. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 138 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.0% probability of exploitation in the next 30 days, higher than 13.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-05-20

Is CVE-2026-5947 being exploited?

It currently carries a trending score of 8 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-5947

No vendor patch reference has been recorded for CVE-2026-5947 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-5947

1 tracked threat in the Threadlinqs corpus references CVE-2026-5947, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Seeded from cveorg and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.