ISC BIND up to 9.18.50/9.20.27 named use after free

Summaryinfo

A vulnerability, which was classified as critical, has been found in ISC BIND up to 9.18.50/9.20.27. The affected element is an unknown function of the component named. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2026-19662. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in ISC BIND up to 9.18.50/9.20.27. It has been rated as critical. This issue affects an unknown functionality of the component named. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is availability. The summary by CVE is:

An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

The advisory is shared at kb.isc.org. The identification of this vulnerability is CVE-2026-19662 since 08/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/16/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Domain Name Software

Vendor

• ISC

Name

• BIND

Version

• 9.18.0
• 9.18.1
• 9.18.2
• 9.18.3
• 9.18.4
• 9.18.5
• 9.18.6
• 9.18.7
• 9.18.8
• 9.18.9
• 9.18.10
• 9.18.11
• 9.18.12
• 9.18.13
• 9.18.14
• 9.18.15
• 9.18.16
• 9.18.17
• 9.18.18
• 9.18.19
• 9.18.20
• 9.18.21
• 9.18.22
• 9.18.23
• 9.18.24
• 9.18.25
• 9.18.26
• 9.18.27
• 9.18.28
• 9.18.29
• 9.18.30
• 9.18.31
• 9.18.32
• 9.18.33
• 9.18.34
• 9.18.35
• 9.18.36
• 9.18.37
• 9.18.38
• 9.18.39
• 9.18.40
• 9.18.41
• 9.18.42
• 9.18.43
• 9.18.44
• 9.18.45
• 9.18.46
• 9.18.47
• 9.18.48
• 9.18.49
• 9.18.50
• 9.20.0
• 9.20.1
• 9.20.2
• 9.20.3
• 9.20.4
• 9.20.5
• 9.20.6
• 9.20.7
• 9.20.8
• 9.20.9
• 9.20.10
• 9.20.11
• 9.20.12
• 9.20.13
• 9.20.14
• 9.20.15
• 9.20.16
• 9.20.17
• 9.20.18
• 9.20.19
• 9.20.20
• 9.20.21
• 9.20.22
• 9.20.23
• 9.20.24
• 9.20.25
• 9.20.26
• 9.20.27

License

• open-source

Website

• Vendor: https://www.isc.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion