| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ISC BIND up to 9.18.49/9.18.50-S1/9.20.26/9.20.27-S1/9.21.24. The affected element is an unknown function of the component Resolver. Performing a manipulation results in resource consumption. This vulnerability is cataloged as CVE-2026-81563. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in ISC BIND up to 9.18.49/9.18.50-S1/9.20.26/9.20.27-S1/9.21.24. This affects some unknown functionality of the component Resolver. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
A BIND resolver encountering an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records may fail to properly deallocate internal resources. If this happens repeatedly, resource exhaustion will eventually prevent the resolver from performing new recursive lookups. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
It is possible to read the advisory at kb.isc.org. This vulnerability is uniquely identified as CVE-2026-81563 since 08/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/16/2026). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 9.18.50, 9.18.50-S1, 9.20.27, 9.20.27-S1 or 9.21.25 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
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-S1
- 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-S1
- 9.21.0
- 9.21.1
- 9.21.2
- 9.21.3
- 9.21.4
- 9.21.5
- 9.21.6
- 9.21.7
- 9.21.8
- 9.21.9
- 9.21.10
- 9.21.11
- 9.21.12
- 9.21.13
- 9.21.14
- 9.21.15
- 9.21.16
- 9.21.17
- 9.21.18
- 9.21.19
- 9.21.20
- 9.21.21
- 9.21.22
- 9.21.23
- 9.21.24
License
Website
- Vendor: https://www.isc.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (isc): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: BIND 9.18.50/9.18.50-S1/9.20.27/9.20.27-S1/9.21.25
Timeline
08/27/2026 CVE reserved09/16/2026 Advisory disclosed
09/16/2026 VulDB entry created
09/16/2026 VulDB entry last update
Sources
Vendor: isc.orgAdvisory: kb.isc.org
Status: Confirmed
CVE: CVE-2026-81563 (🔒)
GCVE (CVE): GCVE-0-2026-81563
GCVE (VulDB): GCVE-100-405939
Entry
Created: 09/16/2026 16:24Changes: 09/16/2026 16:24 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.