{"answers":{"affected":"2 open source packages ship an affected version, including hickory-resolver.","exploited":"There is no known exploitation of GHSA-6w6g-hm98-mhgm in the wild and no public exploit code.","fix":"Upgrade hickory-resolver to 0.26.2 or later.","what":"GHSA-6w6g-hm98-mhgm is a denial of service vulnerability in hickory-resolver, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-6w6g-hm98-mhgm and fix it if it is affected.\n\nWhat it is: GHSA-6w6g-hm98-mhgm is a denial of service vulnerability in hickory-resolver, published on 5 Oct 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 GHSA-6w6g-hm98-mhgm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hickory-resolver (crates.io): affected from 0.26.0-beta.1; fixed in 0.26.2\n- hickory-resolver (crates.io): affected from 0.26.0-beta.1; fixed in 0.26.2\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/GHSA-6w6g-hm98-mhgm/ (Markdown: https://insights.sbomify.com/GHSA-6w6g-hm98-mhgm/index.md)","id":"GHSA-6w6g-hm98-mhgm","markdown":"https://insights.sbomify.com/GHSA-6w6g-hm98-mhgm/index.md","name":"GHSA-6w6g-hm98-mhgm","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust DNS resolver library","requires_auth":"none","summary":"A malicious DNS server can cause a resource-exhaustion denial of service in the hickory-resolver library by triggering an unbounded retry loop on truncated responses.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"When the `hickory-resolver` name server pool implementation receives an upstream response with the TC (truncated) header bit set, it re-queues the request to the same nameserver to retry with UDP transport disabled. However, the retry arm never inspects the transport that just answered and carries no iteration counter. An authoritative server that sets `TC=1` on **every** available transport  keeps the resolver spinning on one persistent TCP connection until the 5s per-request wall-clock deadline expires.\n\n### Reporter\n\nQifan Zhang, Palo Alto Networks","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"hickory-resolver: Unbounded TC-retry loop in `NameServerPool::try_send` (resource-exhaustion DoS)","id":"GHSA-6w6g-hm98-mhgm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.26.2"],"introduced":["0.26.0-beta.1"],"last_affected":[],"package":"hickory-resolver","purl":null,"source":"GHSA-6w6g-hm98-mhgm"},{"ecosystem":"crates.io","fixed":["0.26.2"],"introduced":["0.26.0-beta.1"],"last_affected":[],"package":"hickory-resolver","purl":"pkg:cargo/hickory-resolver","source":"GHSA-6w6g-hm98-mhgm"}],"products":null,"published":"2026-10-05","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious DNS server can cause a resource-exhaustion denial of service in the hickory-resolver library by triggering an unbounded retry loop on truncated responses.","url":"https://insights.sbomify.com/GHSA-6w6g-hm98-mhgm/"}