In some circumstances, when DNSdist is configured to use the nghttp2 library to process incoming DNS over HTTPS
Source GCVE Database
Not known to be exploited · CVSS 3.7 Low.
Data as of 4 Nov 2026, 17:58 UTC
Thin evidence
One scorer or none| CNA (OX) | CVSS 3.1 | 3.7 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 4 Nov 2026.
What to do
AI-suggested
Until a fix is available, consider limiting exposure of DNSdist DoH services to trusted networks or implementing rate limiting to mitigate potential abuse.
Description
A vulnerability in DNSdist occurs when it is configured to use the nghttp2 library for DNS over HTTPS (DoH) queries. An attacker can craft a DoH exchange that triggers an unbounded I/O read loop, leading to excessive CPU consumption and a denial of service condition. The issue has a low severity score and does not impact confidentiality or integrity.