{"answers":{"affected":"4 open source packages ship an affected version, including hickory-recursor.","exploited":"There is no known exploitation of CVE-2026-42254 in the wild and no public exploit code.","fix":"Upgrade hickory-recursor to 0.26.0 or later.","what":"CVE-2026-42254 is a medium-severity vulnerability in Hickory DNS, published on 26 Apr 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-42254 and fix it if it is affected.\n\nWhat it is: CVE-2026-42254 is a medium-severity vulnerability in Hickory DNS, published on 26 Apr 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-42254 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hickory-recursor (crates.io): affected all versions; no fix listed\n- hickory-recursor (crates.io): affected all versions; no fix listed\n- hickory-recursor (crates.io): affected from 0.24.0; fixed in 0.26.0\n- hickory-recursor (crates.io): affected from 0.24.0; fixed in 0.26.0\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-42254/ (Markdown: https://insights.sbomify.com/CVE-2026-42254/index.md)","id":"CVE-2026-42254","markdown":"https://insights.sbomify.com/CVE-2026-42254/index.md","name":"CVE-2026-42254","record":{"aliases":["DEBIAN-CVE-2026-42254","GHSA-2hfw-w5cw-p4g7","GHSA-83hf-93m4-rgwq","UBUNTU-CVE-2026-42254"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"DNS recursor","requires_auth":"none","summary":"Attackers can poison DNS cache entries across zones, leading to incorrect resolution data for users of the Hickory DNS recursor.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"description":"Hickory DNS hickory-recursor 0.1 through 0.25.2 allows cross-zone poisoning because cached data is not directly associated with a query that triggered a response.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in Hickory DNS","id":"CVE-2026-42254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Denial of service in DnsServer","id":"CVE-2026-42255"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":[],"last_affected":[],"package":"hickory-recursor","purl":null,"source":"GHSA-83hf-93m4-rgwq"},{"ecosystem":"crates.io","fixed":[],"introduced":[],"last_affected":[],"package":"hickory-recursor","purl":"pkg:cargo/hickory-recursor","source":"GHSA-83hf-93m4-rgwq"},{"ecosystem":"crates.io","fixed":["0.26.0"],"introduced":["0.24.0"],"last_affected":[],"package":"hickory-recursor","purl":null,"source":"GHSA-83hf-93m4-rgwq"},{"ecosystem":"crates.io","fixed":["0.26.0"],"introduced":["0.24.0"],"last_affected":[],"package":"hickory-recursor","purl":"pkg:cargo/hickory-recursor","source":"GHSA-83hf-93m4-rgwq"}],"prev":{"headline":"Apache ActiveMQ, Apache ActiveMQ Web: HTTP Response Header Injection via JMS Message Properties","id":"CVE-2026-42253"},"products":["Hickory DNS"],"published":"2026-04-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-04-27","vendors":["Hickory Project"]},"summary":"Attackers can poison DNS cache entries across zones, leading to incorrect resolution data for users of the Hickory DNS recursor.","url":"https://insights.sbomify.com/CVE-2026-42254/"}