Quick answers
- Is CVE-2026-123570 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123570 being exploited in the wild.
- How severe is CVE-2026-123570?
- High severity, with a CVSS score of 7.5, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory-Proto 0.18 before 0.26.2.
- Is there a fix for CVE-2026-123570?
- 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-123570 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123570?
- Check whether you run Hickory-Dns Hickory-Proto 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 wire-format parser in hickory-proto preallocates record vectors based on untrusted ANCOUNT, NSCOUNT, and ARCOUNT header fields before validating or reading the actual record data. By sending a UDP datagram with these counts set to 65535, an attacker forces allocation of ~270 bytes × 65535 elements (~18MB) per message. This CWE-770 vulnerability is exploitable remotely without authentication via UDP, and also affects resolvers via spoofed DNS responses.
Affected products
- Hickory DNS hickory-proto 0.18 before 0.26.2
Timeline
- 2026-09-03: disclosed: GitHub security advisory GHSA-67wc-6jq8-ghrc published
- 2026-11-08: advisory: CVE-2026-123570 assigned