{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12617 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-12617 is a high-severity denial of service vulnerability in ISC BIND 9, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12617 and fix it if it is affected.\n\nWhat it is: CVE-2026-12617 is a high-severity denial of service vulnerability in ISC BIND 9, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12617 in the wild and no public exploit code.\n\nAffected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12617/ (Markdown: https://insights.sbomify.com/CVE-2026-12617/index.md)","id":"CVE-2026-12617","markdown":"https://insights.sbomify.com/CVE-2026-12617/index.md","name":"CVE-2026-12617","record":{"aliases":["ALPINE-CVE-2026-12617","AZL-93138","BELL-CVE-2026-12617","DEBIAN-CVE-2026-12617","ECHO-6d4b-e3ee-0962","GHSA-cc7q-gqfw-hrm4","MINI-39rc-x62r-75jr","MINI-mxv3-2pvf-wcx2","UBUNTU-CVE-2026-12617"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"BIND DNS server","requires_auth":"none","summary":"A remote attacker can cause the BIND DNS resolver to crash by sending specific CNAME or DNAME query responses, resulting in a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Record ordering based unexpected exit with CNAME or DNAME","id":"CVE-2026-12617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-12618"},"packages":[],"prev":{"headline":"Other in Eclipse CSI - PIA","id":"CVE-2026-12616"},"products":["BIND 9"],"published":"2026-07-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["ISC"]},"summary":"A remote attacker can cause the BIND DNS resolver to crash by sending specific CNAME or DNAME query responses, resulting in a denial of service.","url":"https://insights.sbomify.com/CVE-2026-12617/"}