Skip to main content
CVE-2026-123589VulnerabilityPublished

hickory-server (hickory-dns) · DNS-over-QUIC (DoQ) server

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123589· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.26.2 when convenient.

Data as of 8 Nov 2026, 06:33 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.15.3
Patch
Available – fixed in 0.26.2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade hickory-dns to 0.26.2.

Affected software

ProductAffectedFixed in
hickory-dnshickory-dnsAffected
  • <0.26.2
Fixed in
  • 0.26.2
crates.iohickory-dnspkg:cargo/hickory-dnsOther threatsAffected
  • <0.26.2
Fixed in
  • 0.26.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade hickory-server (hickory-dns) to version 0.26.2 or later where this issue is fixed. No other mitigation or workaround is indicated in the provided data.

Description

A vulnerability in the DNS-over-QUIC (DoQ) server component of hickory-server (hickory-dns) before version 0.26.2 allows remote unauthenticated clients to open a connection and keep a request stream open indefinitely. This occurs because the server does not apply any timeout when reading a request message from a QUIC stream, bypassing all configured timeouts. This can lead to resource exhaustion and denial of service on the affected server.

References

Community reviews

Loading reviews…