Skip to main content

Hickory DNS CVE-2026-123571

| EUVDEUVD-2026-119456 HIGH
Integer Underflow (CWE-191)
2026-11-08 VulnCheck GHSA-p8hx-6263-88h9
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send crafted TSIG record in DNS wire format
  2. Exploit
    Trigger unchecked subtraction underflow in RDATA decode
  3. Execution
    Panic in overflow-checked build
  4. Impact
    Process crash denial of service

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer underflow checks
Exploitation Conditions

The decisive limiting condition, stated by the GHSA advisory, is build configuration: the underflow only panics in binaries compiled with overflow checks enabled (the Rust dev profile, or release builds with overflow-checks/debug-assertions turned on). Default Rust release builds have overflow checks off, so the subtraction wraps without crashing and the denial of service does not occur. Beyond that, exploitation requires no authentication (PR:N), no user interaction (UI:N), and only the ability to deliver a crafted TSIG record in DNS wire format to a service parsing untrusted DNS messages with vulnerable hickory-proto 0.26.0-0.26.1; the single complete fix is updating to 0.26.2.

Impact

Signals conflict on real-world severity. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a remote, unauthenticated, low-complexity trigger with high availability impact (VA:H) and no confidentiality or integrity impact - consistent with a pure denial-of-service via panic. However, the GHSA advisory materially constrains this: the arithmetic underflow only panics 'when compiling with the dev profile' / with overflow checks enabled. Rust release builds disable overflow checks by default, where the subtraction would wrap silently rather than crash, so the VA:H impact does not apply to typical production binaries unless the operator explicitly enabled overflow-checks/debug-assertions. The vuln.today Decision label is 'this_week' (not act_now or emergency), there is no CISA KEV listing, no EPSS score was provided, and no public exploit was identified - collectively indicating a credible but non-emergency issue. Net: a genuinely high CVSS-scored DoS whose realistic blast radius depends on build configuration; prioritize patching for anyone running debug/overflow-checked builds, treat it as lower urgency for standard release deployments.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a single crafted TSIG resource record in DNS wire format to a service built on vulnerable hickory-proto (0.26.0-0.26.1), causing an unchecked subtraction to underflow during RDATA decoding. On a binary compiled with overflow checks enabled, this triggers an immediate panic that crashes the process, producing denial of service; the low attack complexity (AC:L) means no special timing or grooming is required. No public exploit code was identified, though the trigger is a simple malformed record.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 08, 2026

Malformed TSIG records can crash Hickory DNS 0.26.0 through 0.26.1 builds compiled with overflow checks enabled, causing a denial of service. The flaw is an unchecked subtraction in TSIG RDATA decoding (CWE-191) reachable by unauthenticated remote attackers who can deliver crafted DNS wire-format messages; default Rust release builds have overflow checks off, so the subtraction wraps and the panic does not occur. The assessed CVSS 8.7 reflects high availability impact, but the crash is conditional on build configuration, and no public exploit identified at time of analysis.

RemediationAI

Update hickory-proto to 0.26.2 or later; the GHSA advisory identifies this as the single complete fix (https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-x962-5xwx-fr8x). Deployments that cannot update immediately should note that the panic only occurs in builds with overflow checks enabled, such as the dev profile or release builds with overflow-checks/debug-assertions turned on; binaries using the default release profile (overflow checks off) wrap on the underflow and do not panic. Relying on that build setting is not a complete remediation and forgoes overflow checking for other arithmetic defects, so upgrading to 0.26.2 remains the required action. No other vendor workaround is described in the available references.

Affected VersionsENISA

hickory-dns 0.26.0 <0.26.2

Affected Packages

euvd hickory_dns fix: 0.26.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Hickory DNS is a Rust DNS toolkit, and the vulnerable component is the hickory-proto crate's TSIG record decoder. TSIG (Transaction Signature) RDATA is parsed from untrusted DNS wire-format messages, and a malformed record can drive an unchecked subtraction below zero. CWE-191 (Integer Underflow) means the resulting value wraps in ordinary Rust release builds, where overflow checks are disabled by default; in the dev profile, or release builds with overflow-checks/debug-assertions enabled, the same subtraction triggers a panic. The CPE cpe:2.3:a:hickory-dns:hickory-dns:*:*:*:*:*:*:*:* identifies the affected hickory-dns line, while the GHSA advisory scopes the vulnerable package to rust/hickory-proto 0.26.0 through 0.26.1. The trigger is a crafted TSIG record in DNS wire format, and the advisory does not describe any precondition beyond parsing such a message.

Know when Hickory Dns gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Remote unauthenticated malformed-record trigger is low-complexity (AV:N/AC:L/PR:N/UI:N); impact is availability-only (A:H, C:N/I:N) and realized only in overflow-checked builds.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Nov 08, 2026 - 03:01 EUVD
CVE Published
Nov 08, 2026 - 01:38 cve.org
HIGH 8.7

DescriptionCVE.org

Hickory DNS from 0.26.0 before 0.26.2 contains an integer underflow vulnerability in TSIG RDATA decoding that allows remote attackers to trigger a panic via malformed records. Attackers can send a crafted TSIG record in DNS wire format to cause unchecked subtraction underflow, crashing builds with overflow checks enabled and causing denial of service.

Technical POC Analysis

CWE-191: Integer Underflow (Wrap or Wraparound).

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Hickory DNS versions 0.26.0 through 0.26.1, when compiled with overflow checks enabled, are vulnerable to a denial-of-service condition triggered by malformed TSIG records. This directly impacts service availability for organizations relying on these builds in their DNS infrastructure, potentially disrupting dependent applications and customer-facing services. Leadership should prioritize remediation for internet-facing DNS deployments using affected configurations.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include disabling overflow checks in builds if feasible, restricting network access to DNS services, and employing rate limiting or traffic inspection to block malformed TSIG packets.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
Rust DNS library (hickory/formerly trust-dns), modest ecosystem use, no enterprise-ubiquitous footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Related Vulnerabilities in Hickory DNS Parser Denial of Service Flaws

View all 3
CVE-2026-123587 HIGH
8.9 Nov 08

DNSSEC nonexistence forgery in the Hickory DNS hickory-net crate 0.26.0 and 0.26.1 allows an attacker who can supply DNS

CVE-2026-123608 HIGH
8.7 Nov 08

CPU exhaustion in hickory-proto 0.3.1 through 0.26.0 lets remote attackers force quadratic-time work during DNS message

CVE-2026-123606 HIGH
8.7 Nov 08

Referral fan-out in the Hickory DNS recursor lets remote unauthenticated attackers exhaust recursor resources or flood t

CVE-2026-123577 HIGH
8.7 Nov 08

Hickory DNS (the Rust DNS library formerly known as Trust-DNS), in hickory-server versions 0.24.0 through 0.26.1, buffer

CVE-2026-123576 HIGH
8.7 Nov 08

Memory exhaustion in Hickory DNS 0.24.0 through 0.26.1 allows remote unauthenticated attackers to consume server memory

CVE-2026-123575 HIGH
8.7 Nov 08

Memory exhaustion in Hickory DNS's DNS-over-HTTPS HTTP/2 server before 0.26.2 allows remote unauthenticated attackers to

CVE-2026-123607 HIGH
8.7 Nov 08

Hickory DNS can be driven into an unbounded loop that panics debug builds and exhausts memory in release builds when DNS

CVE-2026-123604 HIGH
8.7 Nov 08

A resource-exhaustion denial of service in the hickory-resolver name server pool (versions 0.26.0-beta.1 through 0.26.1,

CVE-2026-123588 HIGH
8.7 Nov 08

Hickory DNS's recursive resolver can be pushed into a persistent denial-of-service state for a whole zone: when it follo

CVE-2026-123586 HIGH
8.7 Nov 08

Denial of service in the Hickory DNS recursive resolver: unauthenticated remote attackers who control two cyclic sibling

CVE-2026-123574 HIGH
8.7 Nov 08

Denial of service in the Hickory DNS hickory-proto zone file parser: parsing a zone file containing a single token of 40

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy