{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5947 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-5947 is a high-severity use after free vulnerability in Isc Bind, published on 20 May 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-5947 and fix it if it is affected.\n\nWhat it is: CVE-2026-5947 is a high-severity use after free vulnerability in Isc Bind, published on 20 May 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-5947 in the wild and no public exploit code.\n\nAffected product: Isc Bind. 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-5947/ (Markdown: https://insights.sbomify.com/CVE-2026-5947/index.md)","id":"CVE-2026-5947","markdown":"https://insights.sbomify.com/CVE-2026-5947/index.md","name":"CVE-2026-5947","record":{"aliases":["ALPINE-CVE-2026-5947","AZL-87099","BELL-CVE-2026-5947","DEBIAN-CVE-2026-5947","ECHO-e0dd-6c9a-2e1c","GHSA-6mm6-m775-chpm","MINI-w957-5q6j-whqw","UBUNTU-CVE-2026-5947"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"BIND DNS server","requires_auth":"none","summary":"A race condition in BIND's SIG(0) validation during query floods can cause a use-after-free, potentially leading to crashes or code execution.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[{"product":"bind","vendor":"isc"}],"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-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"},{"id":"CWE-416","name":"Use After Free"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Undefined behavior may result due to a race condition leading to a use-after-free violation.  If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature.  If, during that validation, the \"recursive-clients\" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message.\nThis issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1.\nBIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.","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":"SIG(0) validation during query flood may lead to undefined behavior","id":"CVE-2026-5947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"isc:bind","products":["isc:bind"],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Unbounded resend loop in BIND 9 resolver","id":"CVE-2026-5950"},"packages":[],"prev":{"headline":"Invalid handling of CLASS != IN","id":"CVE-2026-5946"},"products":["BIND 9"],"published":"2026-05-20","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0122","kev_date_added":null,"published":"2008-01-16"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0010","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0011","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2001-0013","kev_date_added":null,"published":"2001-05-07"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2000-1029","kev_date_added":null,"published":"2000-11-29"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-1999-0837","kev_date_added":null,"published":"2000-01-04"},{"cvss_score":8.5,"headline":"Denial of service in n/a","id":"CVE-2012-1667","kev_date_added":null,"published":"2012-06-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-09-01","vendors":["ISC"]},"summary":"A race condition in BIND's SIG(0) validation during query floods can cause a use-after-free, potentially leading to crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-5947/"}