Skip to main content
No exploitation reportedFix available

CVE-2026-10846

Insufficient verification that responses belong to a query

No exploitation reported by the sources we read.

  • Published2026-06-10
  • Fixed in1.9.1
  • WeaknessCWE-346

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-06-1007:16CVE publishedNVD

Versions per branch

NVD
Nlnetlabs ldns
BranchAffectedFixed in
1.x≥ 1.2.0, < 1.9.11.9.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As NLnet Labs, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • NLnet Labs ldnsother versions: not affected
    Affected
    • ≥ 1.2.0, < 1.9.1fixed in 1.9.1semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • ldnsUbuntu:Pro:26.04:LTSall versions · fixed in 1.8.4-2ubuntu0.26.04.1~esm1
  • ldnsUbuntu:Pro:24.04:LTSall versions · fixed in 1.8.3-2ubuntu0.1~esm1
  • ldnsUbuntu:Pro:22.04:LTSall versions · fixed in 1.7.1-2ubuntu4+esm2
  • ldnsUbuntu:Pro:20.04:LTSall versions · fixed in 1.7.0-4.1ubuntu1+esm2
  • ldnsUbuntu:Pro:18.04:LTSall versions · fixed in 1.7.0-3ubuntu4.1+esm1
  • ldnsUbuntu:Pro:16.04:LTSall versions · fixed in 1.6.17-8ubuntu0.1+esm2
  • ldnsUbuntu:26.10all versions · no fixed version listed
  • ldnsUbuntu:25.10all versions · no fixed version listed

44 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-10846 Red Hat Product Security243 products fixed · 8 known affected

    ldns: ldns: Off-path poisoning attacks due to insufficient query-response matching

    ldns-devel as a component of Red Hat Enterprise Linux 6 · ldns-doc as a component of Red Hat Enterprise Linux 6 · ldns-python as a component of Red Hat Enterprise Linux 6 · +5 more

  • RHSA-2026:54377 Red Hat Product Security6 products fixed

    Red Hat Security Advisory: ldns security update

  • RHSA-2026:54254 Red Hat Product Security14 products fixed

    Red Hat Security Advisory: ldns security update

  • RHSA-2026:54244 Red Hat Product Security6 products fixed

    Red Hat Security Advisory: ldns security update

  • RHSA-2026:53402 Red Hat Product Security13 products fixed

    Red Hat Security Advisory: ldns security update

  • RHSA-2026:50108 Red Hat Product Security68 products fixed

    Red Hat Security Advisory: ldns security update

2 more advisories

Full record on NVD

Fix

  1. Update Nlnetlabs ldns to 1.9.1
  2. Vendor fix Red Hat Product Security RHSA-2026:54377 · 6 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:54377 · 31 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
  4. No fix available, says the vendor Red Hat Product Security CVE-2026-10846 · 4 productsAffected
  5. No fix planned, says the vendor Red Hat Product Security CVE-2026-10846 · 4 productsWill not fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-06-10
Last Modified
2026-07-23
NVD status
Analyzed
MSRC Title
Insufficient verification that responses belong to a query
GitHub Advisory
GHSA-x77r-8q36-8529

Frequently asked questions

What is CVE-2026-10846?

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.

Is CVE-2026-10846 actively exploited?

Active exploitation of CVE-2026-10846 has not been confirmed. Its EPSS score was 0.1% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-10846?

CVE-2026-10846 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running ldns? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record