{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123582 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-123582 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123582 and fix it if it is affected.\n\nWhat it is: CVE-2026-123582 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123582 in the wild and no public exploit code.\n\nAffected product: hickory-dns. 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-123582/ (Markdown: https://insights.sbomify.com/CVE-2026-123582/index.md)","id":"CVE-2026-123582","markdown":"https://insights.sbomify.com/CVE-2026-123582/index.md","name":"CVE-2026-123582","record":{"aliases":["DEBIAN-CVE-2026-123582","GHSA-8hq4-5836-w6q4","GHSA-p5hq-5ppr-f8g2","UBUNTU-CVE-2026-123582"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The validating recursive resolver and validating forwarder in Hickory DNS (hickory-server) 0.25.0 before 0.26.2 do not check whether the SOA record passed DNSSEC validation when assembling NXDOMAIN or NODATA responses. An attacker able to supply forged DNS responses can have a forged SOA record returned to clients with the AD bit set, misleading clients that rely on the server's DNSSEC validation.","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":"Hickory DNS 0.25.0 before 0.26.2 DNSSEC Validation Bypass via SOA Record","id":"CVE-2026-123582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Hickory DNS 0.25.0 through 0.25.2 Missing Bailiwick Filtering on Negative Responses","id":"CVE-2026-123583"},"nickname":null,"packages":[],"prev":{"headline":"Hickory DNS through 0.26.0-alpha.1 DNSSEC Validation Bypass via Unrelated RRset","id":"CVE-2026-123581"},"products":["hickory-dns"],"published":"2026-11-08","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-09","vendors":["hickory-dns"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123582/"}