CVE-2026-3039
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integrated DNS deployments and/or Kerberos-secured DNS environments. This issue affects BIND 9 versions 9.0.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.9.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| ISC | BIND 9 | 9.0.0 <= 9.16.50 | affected |
| ISC | BIND 9 | 9.18.0 <= 9.18.48 | affected |
| ISC | BIND 9 | 9.20.0 <= 9.20.22 | affected |
| ISC | BIND 9 | 9.21.0 <= 9.21.21 | affected |
| ISC | BIND 9 | 9.9.3-S1 <= 9.16.50-S1 | affected |
| ISC | BIND 9 | 9.18.11-S1 <= 9.18.48-S1 | affected |
| ISC | BIND 9 | 9.20.9-S1 <= 9.20.22-S1 | affected |
Weaknesses
- CWE-771: CWE-771 Missing Reference to Active Allocated Resource
Workarounds
No workarounds known.
ADP Enrichment
CISA ADP Vulnrichment
- SSVC:
- Exploitation: none
- Automatable: yes
- Technical Impact: partial
bind: BIND 9 server memory exhaustion during GSS-API TKEY negotiation
Additional References
- https://access.redhat.com/security/cve/CVE-2026-3039
- https://bugzilla.redhat.com/show_bug.cgi?id=2479767
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3039.json
- https://access.redhat.com/errata/RHSA-2026:24338
- https://access.redhat.com/errata/RHSA-2026:24339
- https://access.redhat.com/errata/RHSA-2026:23360
- https://access.redhat.com/errata/RHSA-2026:24367
- https://access.redhat.com/errata/RHSA-2026:24368
- https://access.redhat.com/errata/RHSA-2026:20334
References
- https://kb.isc.org/docs/cve-2026-3039
- https://downloads.isc.org/isc/bind9/9.18.49
- https://downloads.isc.org/isc/bind9/9.20.23
- https://downloads.isc.org/isc/bind9/9.21.22
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.