# hickory-resolver: Unbounded TC-retry loop in \`NameServerPool::try_send\` (resource-exhaustion DoS)

Advisory record · `GHSA-6w6g-hm98-mhgm`

- **Identifiers:** `GHSA-6w6g-hm98-mhgm`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-406](https://cwe.mitre.org/data/definitions/406.html) · [CWE-835](https://cwe.mitre.org/data/definitions/835.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-406](https://agentprime.io/advisories/tag/cwe-406.md)
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Oct 2026, 22:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `hickory-resolver` (crates.io): affected `>=0.26.0-beta.1, <0.26.2`; fixed in `0.26.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The hickory-resolver crate, versions 0.26.0-beta.1 up to but not including 0.26.2, has an unbounded retry loop when a response has the TC (truncated) bit set. An attacker who controls or can impersonate an authoritative name server can set TC on every transport, causing the resolver to keep retrying over one TCP connection until the 5-second per-request deadline expires, which exhausts resources. Upgrade to hickory-resolver 0.26.2.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6w6g-hm98-mhgm)

## Sources

- [GitHub Advisory Database: GHSA-6w6g-hm98-mhgm](https://github.com/advisories/GHSA-6w6g-hm98-mhgm)
- [OSV: GHSA-6w6g-hm98-mhgm](https://osv.dev/vulnerability/GHSA-6w6g-hm98-mhgm)
- <https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-6w6g-hm98-mhgm>
- <https://github.com/hickory-dns/hickory-dns/pull/3871>
- <https://github.com/hickory-dns/hickory-dns/commit/0848d2e9e4183499343318a690d6dd5e48bc21c1>
- <https://github.com/hickory-dns/hickory-dns/commit/5d37e2e04a36a87013a213b58b820345ef76a263>
- <https://github.com/hickory-dns/hickory-dns>
- <https://github.com/hickory-dns/hickory-dns/releases/tag/v0.26.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6w6g-hm98-mhgm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6w6g-hm98-mhgm/>. Everything for agents: <https://agentprime.io/llms.txt>.