How severe is GHSA-6f2x-v7q7-m7m5?

No CVSS score has been assigned to GHSA-6f2x-v7q7-m7m5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6f2x-v7q7-m7m5?

GHSA-6f2x-v7q7-m7m5 affects the following packages: hickory-resolver (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6f2x-v7q7-m7m5?

Update hickory-resolver to 0.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6f2x-v7q7-m7m5 is resolved across your whole dependency graph.

How do I detect GHSA-6f2x-v7q7-m7m5 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hickory-resolver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6f2x-v7q7-m7m5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6f2x-v7q7-m7m5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6f2x-v7q7-m7m5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6f2x-v7q7-m7m5 published, and has it been updated?

GHSA-6f2x-v7q7-m7m5 was published on October 5, 2026 and was last updated on October 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

hickory-resolver follows irrelevant CNAME records

Real-World Exposure

1 pkg affected

🦀hickory-resolver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hickory-resolver`	≥ 0.25.0&&< 0.26.2	0.26.2`cargo update -p hickory-resolver --precise 0.26.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hickory-resolver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hickory-resolver to 0.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6f2x-v7q7-m7m5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-6f2x-v7q7-m7m5 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

hickory-resolver follows irrelevant CNAME recordsGHSA-6f2x-v7q7-m7m5