- Exploited
- No known exploitation
- Fix
- Fixed in 0.26.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.26.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- High (ghsa)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The hickory-resolver DNS library has a flaw in how it retries truncated responses, which can cause it to loop on a single TCP connection until the request times out. The attacker needs to control or impersonate an authoritative name server that keeps setting the truncation flag on every transport, and the resulting impact is resource exhaustion (denial of service) on the resolver.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
Reporter
Qifan Zhang, Palo Alto Networks
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach16/20hickory-resolver: 2.4M downloads a week
- Severity7/10Rated high by ghsa
- No patch0/5No signal
What would change the score
- Would score about 78 if added to CISA KEV
- Would score about 73 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
Impact
- Widely used
hickory-resolver has 2.4m weekly downloads.Source: crates.io
What to do
Upgrade to a fixed version: 0.26.2.
Timeline
- Advisory published
- Record last updated
Affected versions
- hickory-resolvercrates.io
From 0.26.0-beta.1 · fixed in 0.26.2
Fixed in 0.26.2 (released Sep 3, 2026, 32 days before disclosure).
The latest release, 0.26.3, is not affected.
Evidence 6
- Advisory
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about GHSA-6W6G-HM98-MHGM
Is GHSA-6W6G-HM98-MHGM being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by GHSA-6W6G-HM98-MHGM?
hickory-resolver (crates.io): from 0.26.0-beta.1 before 0.26.2.Source: cve.now feed data
How do I fix GHSA-6W6G-HM98-MHGM?
Upgrade to a fixed version: 0.26.2.Source: cve.now feed data