| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 2.69 |
Summary
A vulnerability was found in ISC BIND 9 up to 9.18.50/9.18.50-S1/9.20.24/9.20.24-S1/9.21.23. It has been rated as critical. Affected by this issue is some unknown functionality of the component Render. The manipulation leads to input validation. This vulnerability is documented as CVE-2026-10822. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in ISC BIND 9 up to 9.18.50/9.18.50-S1/9.20.24/9.20.24-S1/9.21.23 and classified as critical. This issue affects an unknown function of the component Render. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is availability. The summary by CVE is:
If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
The advisory is shared at kb.isc.org. The identification of this vulnerability is CVE-2026-10822 since 06/04/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 $0-$5k at the moment (estimation calculated on 07/22/2026).
Upgrading to version 9.18.50, 9.18.50-S1, 9.20.24, 9.20.24-S1 or 9.21.23 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best 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
- 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.24-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
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.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Input validationCWE: CWE-20
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: BIND 9 9.18.50/9.18.50-S1/9.20.24/9.20.24-S1/9.21.23
Timeline
06/04/2026 CVE reserved07/22/2026 Advisory disclosed
07/22/2026 VulDB entry created
07/22/2026 VulDB entry last update
Sources
Vendor: isc.orgAdvisory: kb.isc.org
Status: Confirmed
CVE: CVE-2026-10822 (🔒)
GCVE (CVE): GCVE-0-2026-10822
GCVE (VulDB): GCVE-100-382361
Entry
Created: 07/22/2026 17:05Changes: 07/22/2026 17:05 (54)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.