Security Vulnerabilities

If you suspect you have found a security defect in BIND or DHCP, or if you wish to inquire about a security issue that you have learned about which has not yet been publicly announced, ISC encourages you to get in touch with our Security Officer by selecting the appropriate pull-down on the Bug Report Form.

Alternatively, you can email us at  However, plain-text e-mail is not a secure choice for communications concerning undisclosed security issues so we ask that you please encrypt your communications to us using the ISC Security Officer public key.

Learn more about Security Vulnerability Disclosure Policy at

Reporting a Bug that is NOT a security vulnerability

  • Please report bugs in BIND 9 by opening an issue in our BIND Gitlab.
  • Please report bugs in Kea at our Kea Trac instance.
  • You may report DHCP bugs, or request features by using the Bug Report Form. You may also use email, if you prefer, by contacting us at

For listing of security vulnerabilities about BIND 9, visit ISC’s Knowledge Base’s BIND 9 Vulnerabilities Matrix.

ISC uses the CVSS, a program of and NIST, to determine the severity of potential security issues.

To subscribe to our Security Vulnerability RSS feed, please subscribe to updates from our knowledgebase at ISC Security Vulnerability RSS Feed


A rarely-used feature in BIND has a flaw which can cause named to exit with an INSIST assertion failure. [...]
Wed, Aug 08, 2018
Source: BIND Security Advisory

[Complete List]


[Complete List]


Last modified: March 2, 2018 at 8:51 am