NLnet Labs Net::DNS forged DNS replies via predictable query IDs
- Exploited
- No known exploitation
- Fix
- Fixed in 1.58
- Who is exposed
- Not reported
Summary
NLnet Labs' Net::DNS generates the 16-bit query IDs it uses to match replies using Perl's built-in rand() function, which makes those IDs predictable. Remotely, without logging in, an attacker who observes a short sequence of query IDs can work out the generator's internal state, predict future IDs, and inject forged responses into the affected Net::DNS instance.
Written by a model
Original description
Net::DNS uses a 16-bit query ID to match responses to the corresponding requests. In versions up to and including 1.57, the ID is obtained from Perl's built-in rand() function. An attacker that can observe the sequence of query IDs is able to expose the internal state of the PNRG and hence predict query IDs before they are transmitted. The victim Net::DNS instance is then exposed to forged responses injected by the attacker. Note that the deduplication cache in 1.57 has no impact on the feasibility of this attack.
What to do
Upgrade to a fixed version: 1.58.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-101340 (Query ID predictable from a short sequence of observations), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-101340 (entry last updated 2026-11-20):
Affected:
- NLnet Labs Net::DNS: from 0.02; from 1.00, fixed in 1.58
Fixed versions: 1.58.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-101340 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101340 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.net-dns.org/downloads/CVE-2026-101340.txt
- https://www.cve.org/CVERecord?id=CVE-2026-101340
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-101340
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-101340"}.Affected versions
- NLnet Labs Net::DNSFrom 0.02; From 1.00 · fixed in 1.58
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-101340 |
| Record | NVD · CVE-2026-101340 |
| Other links 1 | |
| Advisory | net-dns.org · downloads/CVE-2026-101340.txt |
Questions about CVE-2026-101340
Is CVE-2026-101340 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-101340?
Net::DNS: from 0.02; from 1.00 before 1.58.
Source: cve.now feed data
How do I fix CVE-2026-101340?
Upgrade Net::DNS to version 1.58 or later, which the vendor says fixes this issue and all later versions.
Source: cve.org
Related
- CVE-2026-101341Stack overwrite from specially formatted TXT-DATA RDATA field
- CVE-2026-101339Stack overwrite from a specially crafted and formatted HIP RR
- CVE-2026-101338Stack overwrite from a specially crafted and formatted SVCB or HTTPS RR
- CVE-2026-101337Stack overwrite from specially formatted base64 RDATA field
- CVE-2026-109142Krill treats a "local parent" as already-authenticated, letting a CA operator act as any child of any CA on the same server
- CVE-2026-109141Krill users restricted to one CA can make any other CA delegate its prefixes and publish ROAs for them via bulk import
No corrections so far. Something wrong on this page? Report an error.