- 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? →
- 20/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Medium (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 sends extra, unnecessary queries when it follows CNAME records, which increases query amplification beyond what a recursive lookup actually requires. Because the CVSS vector and advisory impact details are not available, the reach and severity of the issue cannot be stated beyond this.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
When the Hickory DNS resolver follows CNAME records, it sends queries that are not necessary to answer the original recursive query. If there are any CNAME records in the authority section or additional section of the response, queries will be sent for those names. If there are any CNAME records that are not part of a CNAME chain starting from the original recursive query name, queries will be sent for those names. This increases query amplification beyond what is necessary to answer the recursive query.
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
- Severity4/10Rated medium by ghsa
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 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.25.0 · 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-6F2X-V7Q7-M7M5
Is GHSA-6F2X-V7Q7-M7M5 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-6F2X-V7Q7-M7M5?
hickory-resolver (crates.io): from 0.25.0 before 0.26.2.Source: cve.now feed data
How do I fix GHSA-6F2X-V7Q7-M7M5?
Upgrade to a fixed version: 0.26.2.Source: cve.now feed data