CISA adds ISC BIND TKEY vulnerability to Known Exploited Vulnerabilities catalog
A denial-of-service flaw in ISC BIND affecting versions prior to 9.9.7-P2 and 9.10.2-P3 has been added to the federal KEV catalog.

Key points
- CVE-2015-5477 allows remote attackers to crash BIND servers via TKEY queries.
- The National Vulnerability Database rates the flaw as High severity with a CVSS score of 7.5.
- Federal agencies must apply mitigations by October 11, 2026, per CISA guidance.
The Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2015-5477 to its Known Exploited Vulnerabilities (KEV) catalog on October 8, 2026. The entry targets a data processing error in ISC BIND that enables remote attackers to cause a denial of service.
At a glance
- CVE
- CVE-2015-5477
- Vendor
- ISC
- Product
- BIND
- CVSS
- 7.5 HIGH
- Weakness
- data processing errors
- Exploited
- Yes (CISA KEV)
- Ransomware use
- Unknown
- Patch deadline (FCEB)
- October 11, 2026
The vulnerability affects ISC BIND 9.x versions prior to 9.9.7-P2 and 9.10.x versions prior to 9.10.2-P3. According to the National Vulnerability Database (NVD), the flaw allows remote attackers to trigger a REQUIRE assertion failure and daemon exit by sending specific TKEY queries. The NVD assigns the vulnerability a CVSS score of 7.5, classifying it as High severity. The weaknesses associated with the flaw are identified as CWE-19 (Information Exposure Through a Directory Listing) and CWE-617 (Synchronization Error in a Threaded Environment).
Context and Background
The addition of CVE-2015-5477 to the KEV catalog mandates specific actions for federal civil executive branch agencies. CISA set a federal due date of October 11, 2026, for compliance. Stakeholders are required to apply mitigations in accordance with vendor instructions. This action must align with CISA’s Binding Operational Directive (BOD) 26-04, which focuses on prioritizing security updates based on risk.
Agencies must also adhere to CISA’s “Forensics Triage Requirements” as outlined in the catalog entry notes. For cloud services, stakeholders must follow applicable BOD 26-04 guidance. If mitigations are unavailable for a specific asset, CISA instructs stakeholders to discontinue use of the product. The catalog entry notes that the use of this vulnerability in ransomware campaigns is currently unknown.
Who is affected
Organizations running ISC BIND versions older than 9.9.7-P2 or 9.10.2-P3 are directly affected. The vulnerability allows remote attackers to disrupt service without requiring authentication. The impact is a denial of service, characterized by the failure of an internal assertion and the subsequent exit of the BIND daemon.
Security professionals must evaluate each asset’s internet exposure to determine risk. The NVD description specifies that the flaw exists in the named versions of ISC BIND 9.x. The specific mechanism involves TKEY queries, which are used for dynamic DNS key management.
What should you do?
Administrators should verify their current BIND version immediately. If running a vulnerable version, apply the vendor-provided mitigations or update to a patched version (9.9.7-P2 or later, or 9.10.2-P3 or later). Federal entities must complete this process by October 11, 2026.
Review CISA’s BOD 26-04 guidance for detailed patching procedures. Ensure compliance with forensics triage requirements if an incident occurs. If a fix is not available for a specific deployment, consider discontinuing the use of the vulnerable product or isolating it from the internet.
What to do and how to stay safe: ISC BIND
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2015-5477?
The National Vulnerability Database rates CVE-2015-5477 with a CVSS score of 7.5, which is classified as High severity.
Which versions of ISC BIND are vulnerable to this flaw?
ISC BIND 9.x versions before 9.9.7-P2 and 9.10.x versions before 9.10.2-P3 are affected by this vulnerability.
What is the federal deadline for mitigating this vulnerability?
The federal due date for applying mitigations for CVE-2015-5477 is October 11, 2026.


