{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3119 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-3119 is a medium-severity denial of service vulnerability in Isc Bind, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3119 and fix it if it is affected.\n\nWhat it is: CVE-2026-3119 is a medium-severity denial of service vulnerability in Isc Bind, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3119 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-3119/ (Markdown: https://insights.sbomify.com/CVE-2026-3119/index.md)","id":"CVE-2026-3119","markdown":"https://insights.sbomify.com/CVE-2026-3119/index.md","name":"CVE-2026-3119","record":{"aliases":["ALPINE-CVE-2026-3119","AZL-80984","BELL-CVE-2026-3119","DEBIAN-CVE-2026-3119","GHSA-rrrp-782c-4484","MINI-fggx-64h4-77w3","UBUNTU-CVE-2026-3119"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"BIND DNS server","requires_auth":"low_privilege","summary":"An authenticated attacker with a valid TSIG key can cause the BIND DNS server to crash by sending a query with a TKEY record.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"isc","cpe":[{"product":"bind","vendor":"isc"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"Under certain conditions, `named` may crash when processing a correctly signed query containing a TKEY record. The affected code can only be reached if an incoming request has a valid transaction signature (TSIG) from a key declared in the `named` configuration.\nThis issue affects BIND 9 versions 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and 9.20.9-S1 through 9.20.20-S1.\nBIND 9 versions 9.18.0 through 9.18.46 and 9.18.11-S1 through 9.18.46-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":"Authenticated query containing a TKEY record may cause named to terminate unexpectedly","id":"CVE-2026-3119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"isc:bind","products":["isc:bind"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RCE in Profelis Informatics' SambaBox","id":"CVE-2026-3120"},"packages":[],"prev":{"headline":"Rhdh: graphql injection leading to platform-wide denial of service (dos) in rh developer hub orchestrator plugin","id":"CVE-2026-3118"},"products":["BIND 9"],"published":"2026-03-25","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-25","vendors":["ISC"]},"summary":"An authenticated attacker with a valid TSIG key can cause the BIND DNS server to crash by sending a query with a TKEY record.","url":"https://insights.sbomify.com/CVE-2026-3119/"}