Hickory-DNS 0.26.0 before 0.26.2 UDP Client Denial of Service via Spoofed Responses
cve-program · CVE-2026-123584
PublishedThe hickory-net crate in Hickory DNS 0.26.0 before 0.26.2 stops listening and returns an error when a client UDP connection receives a datagram that cannot be parsed as a DNS message. Remote attackers who guess the query's source port, without knowing the transaction ID, can spoof malformed responses to abort client queries, causing denial of service.
Read the publisher's advisoryeuvd · EUVD-2026-119343
PublishedThe hickory-net crate in Hickory DNS 0.26.0 before 0.26.2 stops listening and returns an error when a client UDP connection receives a datagram that cannot be parsed as a DNS message. Remote attackers who guess the query's source port, without knowing the transaction ID, can spoof malformed responses to abort client queries, causing denial of service.
Read the publisher's advisorynvd · CVE-2026-123584
PublishedThe hickory-net crate in Hickory DNS 0.26.0 before 0.26.2 stops listening and returns an error when a client UDP connection receives a datagram that cannot be parsed as a DNS message. Remote attackers who guess the query's source port, without knowing the transaction ID, can spoof malformed responses to abort client queries, causing denial of service.
Read the publisher's advisoryosv · RUSTSEC-2026-0517
PublishedWhile waiting for a reply on a UDP connection, the client parsed every datagram that arrived from the name server's address and port before checking its message ID. If parsing failed, the attempt ended with an error instead of dropping the datagram and waiting for the real reply. The receive loop also gave up after three datagrams. An off-path attacker who can guess the client's source port, but not the transaction ID, can send one malformed datagram with a spoofed source address and make the pending lookup fail. The fix reads the message ID from the first two bytes before parsing, ignores short datagrams and datagrams with the wrong ID, keeps listening until the outer timeout, and only then parses the response. It is in 0.26.2.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123584 · CVE overview and exploitation status
cve-program · CVE-2026-123584
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-v44v-c8m4-gc43
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-before-0.26.2-udp-client-denial-of-service-via-spoofed-responses
euvd · EUVD-2026-119343
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-v44v-c8m4-gc43
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-before-0.26.2-udp-client-denial-of-service-via-spoofed-responses
nvd · CVE-2026-123584
- https://github.com/hickory-dns/hickory-dns/security/advisories/GHSA-v44v-c8m4-gc43
- https://www.vulncheck.com/advisories/hickory-dns-0.26.0-before-0.26.2-udp-client-denial-of-service-via-spoofed-responses
osv · RUSTSEC-2026-0517
Related changes
Linked by CVE identifier- Spoofed malformed UDP datagrams abort DNS lookups · Newly collected advisory · 12 Nov 2026
- Hickory-DNS 0.26.0 before 0.26.2 UDP Client Denial of Service via Spoofed Responses · Newly collected advisory · 8 Nov 2026