CVE-2026-10846: NLnet Labs ldns · Origin Validation Error
Affects NLnet Labs ldnsSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.9.1 soon.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.9.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade NLnet Labs ldns to 1.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NLnet Labsldns | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, users should consider using alternative DNS resolver implementations that perform strict response validation or deploy additional network-level protections to mitigate off-path spoofing risks.
Description
NLnet Labs ldns 1.2.0 up to and including versions 1.9.0, when used in applications as (stub) resolver over UDP, lacks matching the query destination address and port with the response source address and port. Furthermore not the query ID, neither the question of the query is matched with that of the response. This makes applications, that use ldns for (stub) resolver functionality over UDP, vulnerable for off-path poisoning attacks. The drill tool, which is shipped with ldns, suffers from this vulnerability.