Bind vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited320 versions
The short answer

Bind is made by Isc. We track 173 published vulnerabilities in it, across 320 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 8 October 2026. If you run Bind, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Bind flaw added to the known-exploited list is CVE-2015-5477, on 8 October 2026. We keep watching the known-exploited list.

Versions

Which versions of Bind do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2015-5477Exploited list, 8 Oct 2026

    ISC BIND Data Processing Errors Vulnerability

    up to 9.9.7up to 9.10.2
Known exploited

Which Bind vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2015-5477HighKnown exploited
    ISC BIND Data Processing Errors Vulnerability

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

    Chance of use>99%Known exploited since8 Oct 2026
Exploit likelihood

Which Bind flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%

    Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue.

    CVSS7.5Published14 Feb 2024
  2. >99%
    CVE-2015-5477HighKnown exploited

    named in ISC BIND 9.x before 9.9.7-P2 and 9.10.x before 9.10.2-P3 allows remote attackers to cause a denial of service (REQUIRE assertion failure and daemon exit) via TKEY queries.

    CVSS7.8Published29 Jul 2015
  3. 93%

    Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server.

    CVSS5.9Published19 May 2020
  4. 89%

    buffer.c in named in ISC BIND 9 before 9.9.9-P3, 9.10.x before 9.10.4-P3, and 9.11.x before 9.11.0rc3 does not properly construct responses, which allows remote attackers to cause a denial of service (assertion...

    CVSS7.5Published28 Sep 2016
  5. 82%

    In BIND 9.5.0 -> 9.11.29, 9.12.0 -> 9.16.13, and versions BIND 9.11.3-S1 -> 9.11.29-S1 and 9.16.8-S1 -> 9.16.13-S1 of BIND Supported Preview Edition, as well as release versions 9.17.0 -> 9.17.1 of the BIND 9.17...

    CVSS9.8Published29 Apr 2021
  6. 64%

    BIND servers are vulnerable if they are running an affected version and are configured to use GSS-TSIG features.

    CVSS8.1Published17 Feb 2021
  7. 63%

    ISC BIND 9.x before 9.9.9-P2, 9.10.x before 9.10.4-P2, and 9.11.x before 9.11.0b2, when lwresd or the named lwres option is enabled, allows remote attackers to cause a denial of service (daemon crash) via a long...

    CVSS5.9Published19 Jul 2016
  8. 62%

    named in ISC BIND 9.x before 9.9.8-P4 and 9.10.x before 9.10.3-P4 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a crafted signature record for a DNAME record, related to...

    CVSS8.6Published9 Mar 2016
  9. 60%

    "deny-answer-aliases" is a little-used feature intended to help recursive server operators protect end users against DNS rebinding attacks, a potential method of circumventing the security model used by client browsers.

    CVSS7.5Published16 Jan 2019
Precursor Intelligence

Running Bind? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 173 published vulnerabilities listed under the name Bind, across 320 versions. The most recent Bind flaw added to the known-exploited list is CVE-2015-5477, on 8 October 2026.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2015-5477.

Each flaw names its own versions, usually as ranges. The newest, CVE-2015-5477, affects up to 9.9.7, up to 9.10.2. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Bind. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.