{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123579 in the wild and no public exploit code.","exposure":"","fix":"Upgrade to a fixed version.","what":"CVE-2026-123579 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123579 and fix it if it is affected.\n\nWhat it is: CVE-2026-123579 is a medium-severity vulnerability in hickory-dns, published on 8 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123579 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-123579/ (Markdown: https://insights.sbomify.com/CVE-2026-123579/index.md)","id":"CVE-2026-123579","markdown":"https://insights.sbomify.com/CVE-2026-123579/index.md","name":"CVE-2026-123579","record":{"aliases":["DEBIAN-CVE-2026-123579","GHSA-vrv5-968r-5ggm","GHSA-xcqq-jfxv-w8jq","UBUNTU-CVE-2026-123579"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-358","name":"Improperly Implemented Security Check for Standard"}],"description":"DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.","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.26.0-beta.1 before 0.26.2 DNSSEC Validation Bypass via Wildcard Expansion","id":"CVE-2026-123579","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.26.0-beta.1 before 0.26.2 DNSSEC Nonexistence Proof Forgery via NSEC3","id":"CVE-2026-123580"},"nickname":null,"packages":[],"prev":{"headline":"Hickory DNS 0.26.0 before 0.26.2 Response Validation Bypass via QDCOUNT=0","id":"CVE-2026-123578"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-08","vendors":["hickory-dns"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123579/"}