CVE-2026-12617

{"id": "CVE-2026-12617", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-12617", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-22T18:48:06.430818Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-officer@isc.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-officer@isc.org", "affectedData": [{"vendor": "ISC", "product": "BIND 9", "versions": [{"status": "affected", "version": "9.18.0", "versionType": "custom", "lessThanOrEqual": "9.18.50"}, {"status": "affected", "version": "9.20.0", "versionType": "custom", "lessThanOrEqual": "9.20.24"}, {"status": "affected", "version": "9.18.11-S1", "versionType": "custom", "lessThanOrEqual": "9.18.50-S1"}, {"status": "affected", "version": "9.20.9-S1", "versionType": "custom", "lessThanOrEqual": "9.20.24-S1"}], "defaultStatus": "unaffected"}]}], "published": "2026-07-22T15:16:51.963", "references": [{"url": "https://downloads.isc.org/isc/bind9/9.20.26", "source": "security-officer@isc.org"}, {"url": "https://kb.isc.org/docs/cve-2026-12617", "source": "security-officer@isc.org"}], "vulnStatus": "Undergoing Analysis", "weaknesses": [{"type": "Secondary", "source": "security-officer@isc.org", "description": [{"lang": "en", "value": "CWE-617"}]}], "descriptions": [{"lang": "en", "value": "The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, `named` may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur.\nThis issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1."}, {"lang": "es", "value": "El problema es la terminaci\u00f3n inesperada del programa basada en el orden y/o el contenido espec\u00edfico en las respuestas a las consultas de registros CNAME o DNAME, y registros A. Espec\u00edficamente, si un cliente consulta por un registro DNAME y un registro A por debajo del DNAME al resolvedor, y el servidor autoritativo responde positivamente a la consulta A pero retrasa la respuesta DNAME y luego responde negativamente, \u2019named\u2019 puede cerrarse inesperadamente. O, si un cliente consulta por un registro CNAME y un registro A para el mismo nombre al resolvedor, y el servidor autoritativo responde positivamente a la consulta A pero retrasa la respuesta CNAME y luego responde con un CNAME autorreferencial, la misma falla puede ocurrir.\nEste problema afecta a las versiones de BIND 9 9.18.0 a 9.18.50, 9.20.0 a 9.20.24, 9.18.11-S1 a 9.18.50-S1, y 9.20.9-S1 a 9.20.24-S1."}], "lastModified": "2026-10-24T18:10:00.163", "sourceIdentifier": "security-officer@isc.org"}