Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-6f2x-v7q7-m7m5

hickory-resolver follows irrelevant CNAME records

CVSS 4.0, no score published

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.

PackageEcosystemAffectedFixed in
hickory-resolvercrates.io>=0.25.0, <0.26.20.26.2
Identifiers
GHSA-6f2x-v7q7-m7m5
Weakness (CWE)
CWE-400
Tags
Published
5 Oct 2026
Updated
5 Oct 2026

Machine-written summary

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

The hickory-resolver package, versions 0.25.0 up to but not including 0.26.2, follows CNAME records that are not needed to answer the original query, including CNAMEs in the authority or additional sections and CNAMEs outside the query's chain. An attacker who can get the resolver to query a malicious or crafted DNS server can cause extra queries to be sent, increasing query amplification. Upgrade to hickory-resolver 0.26.2. The source gives few details on the exact attack conditions.

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

ScoreRatingCVSSVectorSource
Not published None 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

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.