cve.bz

CVE-2026-123575 Hickory DNS before 0.26.2 DoH Memory Exhaustion via Incomplete Request Bodies

8.7 highEPSS 0.4%

High (8.7) in hickory-dns hickory-dns. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Hickory DNS before 0.26.2 contains a resource exhaustion vulnerability in its DNS-over-HTTPS HTTP/2 server that lacks sufficient timeouts or limits for incomplete request bodies. Remote attackers can open DoH connections, send incomplete request bodies, and hold connections open to exhaust server memory.

Severity

CVSS 4.0

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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123575 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123575?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123575?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123575 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-123575

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-123575](https://cve.bz/cve/badge/CVE-2026-123575.svg)](https://cve.bz/cve/CVE-2026-123575)

HTML:

<a href="https://cve.bz/cve/CVE-2026-123575"><img src="https://cve.bz/cve/badge/CVE-2026-123575.svg" alt="CVE-2026-123575"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hickory-dnsbefore 0.26.2

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13rust-hickory-dnsno fix listedDEBIAN-CVE-2026-123575
Debian14rust-hickory-dns0.26.3-1DEBIAN-CVE-2026-123575
Ubuntu26.04:LTS, 26.10rust-hickory-dnsno fix listedUBUNTU-CVE-2026-123575

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON