{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40776 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-40776 is a high-severity vulnerability in ISC BIND 9, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40776 and fix it if it is affected.\n\nWhat it is: CVE-2025-40776 is a high-severity vulnerability in ISC BIND 9, published on 16 Jul 2025. 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-2025-40776 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-2025-40776/ (Markdown: https://insights.sbomify.com/CVE-2025-40776/index.md)","id":"CVE-2025-40776","markdown":"https://insights.sbomify.com/CVE-2025-40776/index.md","name":"CVE-2025-40776","record":{"aliases":["ALPINE-CVE-2025-40776","BELL-CVE-2025-40776","GHSA-2hm8-9847-q7gc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"DNS resolver software","requires_auth":"none","summary":"Attackers can poison the cache of a BIND 9 resolver configured with EDNS Client Subnet, leading to incorrect DNS responses.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-349","name":"Acceptance of Extraneous Untrusted Data With Trusted Data"}],"description":"A `named` caching resolver that is configured to send ECS (EDNS Client Subnet) options may be vulnerable to a cache-poisoning attack.\nThis issue affects BIND 9 versions 9.11.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.37-S1, and 9.20.9-S1 through 9.20.10-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":"Birthday Attack against Resolvers supporting ECS","id":"CVE-2025-40776","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"A possible assertion failure when 'stale-answer-client-timeout' is set to '0'","id":"CVE-2025-40777"},"packages":[],"prev":{"headline":"DNS message with invalid TSIG causes an assertion failure","id":"CVE-2025-40775"},"products":["BIND 9"],"published":"2025-07-16","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":"2025-07-22","vendors":["ISC"]},"summary":"Attackers can poison the cache of a BIND 9 resolver configured with EDNS Client Subnet, leading to incorrect DNS responses.","url":"https://insights.sbomify.com/CVE-2025-40776/"}