Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-10846
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 07:32 UTC · Revision 1
Source evidence
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.
osv:CVE-2026-10846
Complete source record
{
"id": "d293f79f03bb7692003321836c23cf568ae801b71c9074765655887ce48778ad",
"url": "https://osv.dev/vulnerability/CVE-2026-10846",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2026-10846",
"summary": "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.",
"evidence": "osv:CVE-2026-10846",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-10846",
"aliases": [
"CVE-2026-10846"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/nlnetlabs/ldns",
"type": "GIT",
"events": [
{
"introduced": "d6f0b478cabfd4fa0b28a90bd8b0209fe38684bd"
},
{
"fixed": "1867b1d7719424e1ab91e3f3827794b4bf849dc6"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:nlnetlabs:ldns:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "1.2.0"
},
{
"fixed": "1.9.1"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-10846.json"
}
}
],
"modified": "2026-10-24T10:30:54.493368835Z",
"provider": "osv",
"references": [
"https://www.nlnetlabs.nl/downloads/ldns/CVE-2026-10846.txt"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2026-10846",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 438203,
"published_at": "2026-06-10T07:16:24.443+00:00"
}