← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2015-5477 exploited? Yes: in CISA KEV since 8 Oct 2026

Gociux · ISC BIND · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2015-5477, ISC BIND Data Processing Errors Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 8 Oct 2026, 4089 days after it was published. It affects ISC BIND. If you run it, CISA's required action is: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

exploitedYesCISA KEV · 8 Oct 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity7.5CVSS 3.1 · high
US federal due11 Oct 2026BOD 22-01 deadline

What it is

ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.

VendorISC (1 exploited CVE in KEV)
ProductBIND
Vulnerability ISC BIND Data Processing Errors Vulnerability
WeaknessCWE-19
Published29 Jul 2015
Added to KEV8 Oct 2026
Reported by (CNA)mitre

What to do

  1. Check whether you run it. Look for BIND in your asset inventory, including appliances and cloud images. Stack check lists every exploited ISC CVE at once.
  2. Apply the fix. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 29 Jul 2015.
  4. Get told next time. Email alerts when CISA adds a CVE for ISC.

References

Questions

Is CVE-2015-5477 being exploited?

Yes. CISA added CVE-2015-5477 to the Known Exploited Vulnerabilities catalog on 8 Oct 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2015-5477 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2015-5477?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Check ISC's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected BIND and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in October 2026 · act-now radar.

Running ISC in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →