CVE-2015-5477: ISC BIND Data Processing Errors Vulnerability
ISC · BIND
Listed by CISA as exploited in the wild since 8 Oct 2026. Below: exploitation status, EPSS and every published CVSS, each with its source, then affected versions and references.
Build snapshot collected · KEV catalog 2026.10.21 · EPSS of 21 Oct 2026 · not a live feed: collected once, at build time
Description
as written by CISA (KEV catalog)
ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.
Required action
CISA KEV
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.
Affected products and versions
CVE record · mitre
n/a · n/a
- affected: n/a
Status words (affected, unaffected, unknown) and version bounds are copied from the record. An upper bound such as “before 7.1.0” usually marks the first fixed version; confirm in the vendor advisory before planning an upgrade.
References
CISA KEV notes and CVE record
- https://web.archive.org/web/20150729014733/https://kb.isc.org/article/AA-01272
- https://access.redhat.com/errata/RHSA-2015:1513.html
- https://supportportal.juniper.net/s/article/2016-01-Security-Bulletin-Junos-Vulnerability-in-ISC-BIND-named-CVE-2015-5477
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2015-5477
- http://packetstormsecurity.com/files/132926/BIND-TKEY-Query-Denial-Of-Service.html
- http://www.oracle.com/technetwork/topics/security/ovmbulletinjul2016-3090546.html
- http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00050.html
- https://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04789415
- https://kb.juniper.net/JSA10783
- http://rhn.redhat.com/errata/RHSA-2015-1513.html
EPSS over the last 30 days
See also: the full KEV catalog
Related entries
Questions about CVE-2015-5477
Is CVE-2015-5477 being exploited?
Yes, according to CISA. CVE-2015-5477 was added to the Known Exploited Vulnerabilities catalog on 8 Oct 2026, which CISA does only with reliable evidence of exploitation in the wild. The catalog field for ransomware campaign use says "Unknown".
What is the deadline to remediate CVE-2015-5477?
CISA set 11 Oct 2026 as the due date for US Federal Civilian Executive Branch agencies. The date is binding only for those agencies; other organisations can read it as a measure of urgency.
What is the EPSS score of CVE-2015-5477?
99.4%, in the 99.9th percentile, in the FIRST EPSS model of 21 Oct 2026. It estimates the probability of exploitation activity in the following 30 days. For a CVE already in KEV the score is secondary: exploitation has been observed.
How severe is CVE-2015-5477?
CISA-ADP rates it 7.5 HIGH (CVSS 3.1). These are the published assessments as of 22 Oct 2026; this site does not rescore.
Which product does CVE-2015-5477 affect?
ISC BIND, as named in the CISA catalog. The affected versions listed in the CVE record are on this page; the vendor advisory in the references is the authority on fixed versions.
Related sections
- WatchlistWhat attackers started using this month, most urgent first.
- Exploited catalogEvery flaw CISA lists as used in real attacks (KEV), searchable.
- CVE lookupType one identifier: attack status, probability, severity, versions.
- Attack probabilityEPSS score for up to 100 identifiers at once.
- VendorsWhich vendors have the most exploited flaws.
- RSS and JSON feedsFollow new exploited flaws for the vendors you run.
- Sources and methodWhere each number comes from and how the order is decided.