Quick answers
- Is CVE-2026-123575 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123575 being exploited in the wild.
- How severe is CVE-2026-123575?
- High severity, with a CVSS score of 7.5, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory DNS before 0.26.2.
- Is there a fix for CVE-2026-123575?
- Yes: fixed in 0.26.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123575 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123575?
- Check whether you run Hickory-Dns Hickory DNS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.26.2
Technical details
The DNS-over-HTTPS HTTP/2 server in Hickory DNS lacks sufficient timeouts and limits for incomplete request bodies, enabling resource exhaustion attacks. Remote, unauthenticated attackers can exploit this by opening multiple DoH connections, sending incomplete request bodies, and keeping them open to consume unbounded server memory. A fix is available in version 0.26.2 and later.
Affected products
- Hickory DNS Hickory DNS before 0.26.2
Timeline
- 2026-09-03: disclosed: Security advisory published on GitHub
- 2026-11-08: advisory: CVE-2026-123575 published