CVE-2026-10822 Internet Systems Consortium CVE debrief

Who should care

Organizations using 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 should review and apply patches to mitigate this vulnerability. Additionally, security teams and operators responsible for BIND 9 deployments should be aware of the potential impact and take necessary actions to protect their systems.

Technical summary

BIND 9 encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. 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 vulnerability is related to the handling of DNS records with invalid data structures, which can lead to service disruption.

Defensive priority

Medium priority due to CVSS score of 6.5 and potential for service disruption.

Recommended defensive actions

• Review and apply patches for 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
• Monitor BIND 9 services for abnormal termination
• Implement compensating controls such as DNS query logging and monitoring
• Verify BIND 9 deployments in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Limited information is available on known affected scope and vendor remediation. Organizations should verify their BIND 9 deployments and review vendor guidance for patching and mitigation strategies. Evidence is limited, and defenders should focus on verifying affected systems and applying patches. The CVE record and NVD entry provide further details, but additional information on affected scope and vendor remediation is needed.

Official resources