CVE-2026-10846: Insufficient verification that responses belong to a query
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: NLnet Labs ldns 1.9.1; azl3 ldns 1.8.3-2 on Azure Linux 3.0 1.8.3-3.
Low priority for now. Upgrade to NLnet Labs ldns 1.9.1; azl3 ldns 1.8.3-2 on Azure Linux 3.0 1.8.3-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-12817
- ALSA-2026:49520
- ALSA-2026:49836
- ALSA-2026:50108
- openSUSE-SU-2026:10998-1
- openSUSE-SU-2026:21093-1
- 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
- Published
- Jun 10, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-346
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · NLnet Labs
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nlnetlabs | ldns | cpe:2.3:a:nlnetlabs:ldns |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nlnetlabs ldns1.2.0 and later · before 1.9.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (NLnet Labs). Independent of NVD's CPE analysis and usually ahead of it.
NLnet Labs ldns
- 1.2.0 and later · before 1.9.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | ldns | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:10 | ldns-devel | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:10 | ldns-doc | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:10 | ldns-utils | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:10 | perl-ldns | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:10 | python3-ldns | before 1.8.3-18.el10_2.1 | 1.8.3-18.el10_2.1 |
| AlmaLinux:8 | ldns | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:8 | ldns-devel | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:8 | ldns-doc | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:8 | ldns-utils | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:8 | perl-ldns | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:8 | python3-ldns | before 1.7.0-23.el8_10 | 1.7.0-23.el8_10 |
| AlmaLinux:9 | ldns | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| AlmaLinux:9 | ldns-devel | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| AlmaLinux:9 | ldns-doc | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| AlmaLinux:9 | ldns-utils | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| AlmaLinux:9 | perl-ldns | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| AlmaLinux:9 | python3-ldns | before 1.7.1-12.el9_8.1 | 1.7.1-12.el9_8.1 |
| Debian:12 | ldns | from 0 | — |
| Debian:14 | ldns | before 1.9.2-1 | 1.9.2-1 |
| openSUSE:Leap 16.0 | ldns | before 1.8.4-160000.3.1 | 1.8.4-160000.3.1 |
| openSUSE:Tumbleweed | ldns | before 1.9.2-1.1 | 1.9.2-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | ldns | before 0:1.8.3-18.el10_0.1 | 0:1.8.3-18.el10_0.1 |
| Red Hat:enterprise_linux_eus:10.0 | perl-ldns | before 0:1.8.3-18.el10_0.1 | 0:1.8.3-18.el10_0.1 |
+45
Same product
nlnetlabs: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-1000232A double-free vulnerability in str2host.c in ldns 1.7.0 have unspecified impact and attack vectors.40Plan
- CVE-2017-1000231A double-free vulnerability in parse.c in ldns 1.7.0 have unspecified impact and attack vectors.40Plan
- CVE-2020-19861When a zone file in ldns 1.7.1 is parsed, the function ldns_nsec3_salt_data is too trusted for the length value obtained from the zone file.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-3581Nov 4, 2011 · Heap-based buffer overflow in the ldns_rr_new_frm_str_internal function in ldns before 1.6.11 allows remote attackers to cause a denial of s28Monitor
- ← EarlierCVE-2014-3209Nov 15, 2014 · The ldns-keygen tool in ldns 1.6.x uses the current umask to set the privileges of the private key, which might allow local users to obtain 8Monitor
- ← EarlierCVE-2020-19860Jan 21, 2022 · When ldns version 1.7.1 verifies a zone file, the ldns_rr_new_frm_str_internal function has a heap out of bounds read vulnerability.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| NLnet Labs ldns | 1.9.1 | Vendor (CNA) |
| azl3 ldns 1.8.3-2 on Azure Linux 3.0 | 1.8.3-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:ldns | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:ldns-devel | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:ldns-doc | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:ldns-utils | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:perl-ldns | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3-ldns | 1.7.0-23.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:ldns | 1.9.2-1 · Debian:14 | Package registry (OSV) |
| opensuse:ldns | 1.9.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:ldns | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:ldns-debuginfo | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:ldns-debugsource | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:ldns-devel | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:ldns-doc | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:ldns-utils | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:ldns-utils-debuginfo | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:perl-ldns | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:perl-ldns-debuginfo | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:python3-ldns | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:python3-ldns-debuginfo | 0:1.7.0-23.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:ldns | 0:1.7.0-23.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| suse:ldns | 1.8.4-160000.3.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Pablo Ruiz'codecome.ai'finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-346 · Origin Validation ErrorCVSS 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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Exploit Script-Based APIsCAPEC-160Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-Middle: ARP Cache PoisoningT1557.002
- Compromise Infrastructure: DNS ServerT1584.002
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.