Quick answers
- Is CVE-2026-123584 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123584 being exploited in the wild.
- How severe is CVE-2026-123584?
- Medium severity, with a CVSS score of 5.9, published 8 November 2026.
- Which products and versions are affected?
- Hickory-Dns Hickory-Net 0.26.0 before 0.26.2.
- Is there a fix for CVE-2026-123584?
- Yes: fixed in hickory-net 0.26.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123584 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-123584?
- Check whether you run Hickory-Dns Hickory-Net 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: hickory-net 0.26.2
Technical details
The hickory-net crate improperly handles malformed DNS datagrams on UDP client connections; when a datagram cannot be parsed as a valid DNS message, the listener stops and returns an error rather than discarding the invalid packet and continuing. An attacker needs only to guess the source port (not the transaction ID) to spoof a malformed response that triggers this condition. This is a variant of the TuDoor attack that affects UDP DNS client availability.
Affected products
- Hickory DNS hickory-net 0.26.0 before 0.26.2
Timeline
- 2026-09-03: disclosed: GitHub Security Advisory GHSA-v44v-c8m4-gc43 published
- 2026-11-08: advisory: NVD entry CVE-2026-123584 published