Skip to main content
CVE-2026-123579VulnerabilityPublished Updated

Rust hickory proto: DNSSEC validation

Affects rust-hickory-protoSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123579· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium.

Data as of 18 Nov 2026, 15:20 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10rust-hickory-netpkg:deb/ubuntu/rust-hickory-net?arch=source&distro=stonkingOther threatsAffected
  • =0.26.1-1
Fixed in–
Ubuntu 26.10rust-hickory-protopkg:deb/ubuntu/rust-hickory-proto?arch=source&distro=stonkingOther threatsAffected
  • =0.24.4-6
  • =0.26.1-1
Fixed in–
Ubuntu 26.04 LTSrust-hickory-protopkg:deb/ubuntu/rust-hickory-proto?arch=source&distro=resoluteOther threatsAffected
  • =0.24.4-4.1
  • =0.24.4-6
Fixed in–
Ubuntu 24.04 LTSrust-hickory-protopkg:deb/ubuntu/rust-hickory-proto?arch=source&distro=nobleOther threatsAffected
  • =0.24.0-1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

DNSSEC validation in Hickory DNS hickory-net 0.26.0-beta.1 before 0.26.2 and hickory-proto through 0.26.0-alpha.1 does not distinguish NODATA responses from wildcard-expanded positive responses. For a query that should return NODATA in a zone with wildcard records, an attacker can combine an NSEC3 record matching the query name with a signed wildcard record into a bogus positive response that validation accepts.

References

Community reviews

Loading reviews…