# CVE-2026-10846: Insufficient verification that responses belong to a query > Attackers can poison DNS responses in applications using ldns over UDP due to insufficient verification of response origin and content. - **Severity:** High 8.2 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jun 2026 - **Updated:** 10 Jun 2026 - **Also known as:** ALSA-2026:49520, ALSA-2026:49836, ALSA-2026:50108, AZL-89715, CLSA-2026-1784215324, CLSA-2026-1784986614, DEBIAN-CVE-2026-10846, GHSA-x77r-8q36-8529, OESA-2026-2788, RHSA-2026:49520, RHSA-2026:49836, RHSA-2026:50108, RHSA-2026:53402, RHSA-2026:54244, RHSA-2026:54254, RHSA-2026:54377, RLSA-2026:49520, RLSA-2026:49836, RLSA-2026:50108, SUSE-SU-2026:22167-1, SUSE-SU-2026:2461-1, SUSE-SU-2026:2462-1, UBUNTU-CVE-2026-10846, USN-8449-1, openSUSE-SU-2026:10998-1, openSUSE-SU-2026:21093-1 ## What is CVE-2026-10846? CVE-2026-10846 is a high-severity vulnerability in NLnet Labs ldns, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-346 (Origin Validation Error) ## Which versions are affected by CVE-2026-10846? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ldns` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `ldns-devel` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `ldns-doc` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `ldns-utils` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `perl-ldns` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `python3-ldns` | AlmaLinux:10 | All versions | 1.8.3-18.el10_2.1 | | `ldns` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `ldns-devel` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `ldns-doc` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `ldns-utils` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `perl-ldns` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `python3-ldns` | AlmaLinux:8 | All versions | 1.7.0-23.el8_10 | | `ldns` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `ldns-devel` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `ldns-doc` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `ldns-utils` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `perl-ldns` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `python3-ldns` | AlmaLinux:9 | All versions | 1.7.1-12.el9_8.1 | | `ldns` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-doc` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-utils` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns-utils-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `perl-ldns` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `perl-ldns-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `python3-ldns` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `python3-ldns-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:1.8.3-18.el10_2.1 | | `ldns` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `ldns-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `ldns-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `ldns-utils-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `perl-ldns-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `python3-ldns-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.7.0-23.el8_10 | | `ldns-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.0-23.el8_10 | | `ldns-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.0-23.el8_10 | | `ldns-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.0-23.el8_10 | | `ldns-doc` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.0-23.el8_10 | | `ldns-utils` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.7.0-23.el8_10 | Products: Nlnetlabs Ldns. ## How do I fix CVE-2026-10846? Upgrade to a fixed version. ## Is CVE-2026-10846 being exploited? There is no known exploitation of CVE-2026-10846 in the wild and no public exploit code. ## Other vulnerabilities in NLnet Labs ldns - [CVE-2017-1000231](https://insights.sbomify.com/CVE-2017-1000231/): Use after free in n/a (critical 9.8) - [CVE-2017-1000232](https://insights.sbomify.com/CVE-2017-1000232/): Use after free in n/a (critical 9.8) - [CVE-2020-19861](https://insights.sbomify.com/CVE-2020-19861/): Information disclosure in n/a (high 7.5) - [CVE-2011-3581](https://insights.sbomify.com/CVE-2011-3581/): Memory corruption in n/a (medium 6.8) - [CVE-2020-19860](https://insights.sbomify.com/CVE-2020-19860/): Information disclosure in n/a (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-10846 and fix it if it is affected. What it is: CVE-2026-10846 is a high-severity vulnerability in NLnet Labs ldns, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-10846 in the wild and no public exploit code. Affected product: NLnet Labs ldns. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-10846/ (Markdown: https://insights.sbomify.com/CVE-2026-10846/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10846 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10846 - OSV: https://osv.dev/vulnerability/CVE-2026-10846 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10846/ Summaries are generated and may contain mistakes; the official description above is the record.