CVE-2026-101340: Net::DNS uses a 16-bit query ID to match responses to the corresponding requests
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 1.58 as a priority.
Data as of 20 Nov 2026, 16:21 UTC
Thin evidence
One scorer or none| CNA (NLnet Labs) | CVSS 4.0 | 9.1 |
|---|
- Patch
- Available – fixed in 1.58
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 19 Nov 2026.
What to do
Upgrade Net::DNS to 1.58.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NLnet LabsNet::DNS | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should consider mitigating exposure by limiting attacker ability to observe DNS query IDs, for example by restricting network visibility or using DNS over secure channels. Avoid relying on the deduplication cache as a mitigation.
Description
Net::DNS versions up to and including 1.57 use a 16-bit query ID generated by Perl's built-in rand() function to match DNS responses to requests. An attacker who can observe the sequence of query IDs can expose the internal state of the pseudorandom number generator (PRNG) and predict future query IDs. This allows the attacker to inject forged DNS responses to the victim, bypassing the intended matching mechanism. The deduplication cache in version 1.57 does not mitigate this attack.