Advisory

RUSTSEC-2026-0518

Also known as: CVE-2026-123592, GHSA-rx82-4p2j-j5cv

Summary

DNSSEC validation cache could reuse an Insecure result for a different name

Details

The DNSSEC validation cache used a 64-bit hash of the query as its key, and two keys with the same hash counted as equal. The Hash implementation of Name hashed the bytes of the labels but not where one label ends and the next begins, so names that differ only in the placement of dots (such as ab.c. and a.bc.) hashed to the same value.

An attacker who controls an unsigned delegation whose name collides in this way with a name in a signed zone can first get an Insecure result cached for their own name. A forged response for the signed name is then served from that cache entry without signature checks and returned with the AD bit clear, where validation should have failed.

This affects DNSSEC validation through DnssecDnsHandle when built with dnssec-ring or dnssec-aws-lc-rs.

The fix stores the query in the cache key and compares it on lookup. The Hash implementations of Label, Name and LowerName in hickory-proto were also changed to include label boundaries. Both are in 0.26.2.

Severity

Not rated by the source.

Dates

Published
2026-09-03 12:00 UTC
Modified
2026-11-12 14:30 UTC

Affected packages and fixes

hickory-net

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.26.2 (semver)

Fixed versions

0.26.2

Fix

  • Fixed version 0.26.2
    cargo update -p hickory-net --precise 0.26.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences