CVE-2026-10846

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-10. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 23, 2026

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-ldns (1.7.1-2ubuntu4+esm2) @ jammy2026-08-21ubuntu
redhatldns-0:1.7.1-11.el9_2.12026-08-12redhat
redhatldns-0:1.7.1-12.el9_6.12026-08-12redhat
redhatldns-0:1.7.1-11.el9_4.12026-08-12redhat
redhatldns-0:1.8.3-18.el10_0.12026-08-11redhat
redhatldns-0:1.7.1-12.el9_8.12026-08-04redhat
redhatldns-0:1.8.3-18.el10_2.12026-08-04redhat
redhatldns-0:1.7.0-23.el8_102026-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ldns1.7.1-2 ... 1.9.2-1 (12 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ldns1.8.3-1 ... 1.9.2-1 (8 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ldns1.8.4-2, 1.9.0-1, 1.9.2-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ldns1.8.4-2, 1.9.0-11.9.2-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 34× in last 7d / 139× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 322 total refreshes for this CVE.

  1. 2026-08-21 06:40 UTCEG score recompute
  2. 2026-08-21 06:40 UTCVendor advisory
  3. 2026-08-21 06:40 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 19:47 UTCVendor advisory
  6. 2026-08-20 19:47 UTCGHSA enrichment
  7. 2026-08-20 08:54 UTCEG score recompute
  8. 2026-08-20 08:54 UTCVendor advisory
  9. 2026-08-20 08:54 UTCGHSA enrichment
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-19 15:03 UTCEG score recompute
  12. 2026-08-19 15:03 UTCVendor advisory
  13. 2026-08-19 15:03 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 10:38 UTCVendor advisory
  16. 2026-08-17 10:38 UTCGHSA enrichment
  17. 2026-08-16 23:41 UTCEG score recompute
  18. 2026-08-16 23:41 UTCVendor advisory
  19. 2026-08-16 23:41 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 10:55 UTCEG score recompute
  22. 2026-08-16 10:55 UTCVendor advisory
  23. 2026-08-16 10:55 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-16 00:03 UTCVendor advisory
Show 75 more
  1. 2026-08-16 00:03 UTCGHSA enrichment
  2. 2026-08-15 11:00 UTCEG score recompute
  3. 2026-08-15 11:00 UTCVendor advisory
  4. 2026-08-15 11:00 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 23:28 UTCVendor advisory
  7. 2026-08-14 23:28 UTCGHSA enrichment
  8. 2026-08-14 12:35 UTCVendor advisory
  9. 2026-08-14 12:35 UTCGHSA enrichment
  10. 2026-08-14 01:42 UTCEG score recompute
  11. 2026-08-14 01:42 UTCVendor advisory
  12. 2026-08-14 01:42 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 14:49 UTCVendor advisory
  15. 2026-08-13 14:49 UTCGHSA enrichment
  16. 2026-08-13 03:03 UTCVendor advisory
  17. 2026-08-13 03:03 UTCGHSA enrichment
  18. 2026-08-12 16:10 UTCEG score recompute
  19. 2026-08-12 16:10 UTCVendor advisory
  20. 2026-08-12 16:10 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-12 05:12 UTCVendor advisory
  23. 2026-08-12 05:12 UTCGHSA enrichment
  24. 2026-08-11 17:58 UTCEG score recompute
  25. 2026-08-11 17:58 UTCVendor advisory
  26. 2026-08-11 17:58 UTCGHSA enrichment
  27. 2026-08-11 13:42 UTCEPSS rescore
  28. 2026-08-11 07:02 UTCEG score recompute
  29. 2026-08-11 07:02 UTCVendor advisory
  30. 2026-08-11 07:02 UTCGHSA enrichment
  31. 2026-08-10 23:59 UTCEPSS rescore
  32. 2026-08-10 20:09 UTCVendor advisory
  33. 2026-08-10 20:09 UTCGHSA enrichment
  34. 2026-08-10 08:53 UTCVendor advisory
  35. 2026-08-10 08:53 UTCGHSA enrichment
  36. 2026-08-09 22:01 UTCEG score recompute
  37. 2026-08-09 22:01 UTCVendor advisory
  38. 2026-08-09 22:01 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 11:08 UTCVendor advisory
  41. 2026-08-09 11:08 UTCGHSA enrichment
  42. 2026-08-09 00:15 UTCVendor advisory
  43. 2026-08-09 00:15 UTCGHSA enrichment
  44. 2026-08-08 13:22 UTCVendor advisory
  45. 2026-08-08 13:22 UTCGHSA enrichment
  46. 2026-08-08 02:28 UTCVendor advisory
  47. 2026-08-08 02:28 UTCGHSA enrichment
  48. 2026-08-07 15:35 UTCVendor advisory
  49. 2026-08-07 15:35 UTCGHSA enrichment
  50. 2026-08-07 04:42 UTCVendor advisory
  51. 2026-08-07 04:42 UTCGHSA enrichment
  52. 2026-08-06 17:49 UTCEG score recompute
  53. 2026-08-06 17:49 UTCVendor advisory
  54. 2026-08-06 17:48 UTCGHSA enrichment
  55. 2026-08-06 13:46 UTCEPSS rescore
  56. 2026-08-06 06:55 UTCVendor advisory
  57. 2026-08-06 06:55 UTCGHSA enrichment
  58. 2026-08-05 20:02 UTCEG score recompute
  59. 2026-08-05 20:02 UTCVendor advisory
  60. 2026-08-05 20:02 UTCGHSA enrichment
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-04 15:57 UTCEG score recompute
  63. 2026-08-04 15:57 UTCVendor advisory
  64. 2026-08-04 15:57 UTCGHSA enrichment
  65. 2026-08-04 15:09 UTCEPSS rescore
  66. 2026-08-04 01:46 UTCVendor advisory
  67. 2026-08-04 01:46 UTCGHSA enrichment
  68. 2026-08-03 14:53 UTCEG score recompute
  69. 2026-08-03 14:53 UTCVendor advisory
  70. 2026-08-03 14:53 UTCGHSA enrichment
  71. 2026-08-03 10:35 UTCEPSS rescore
  72. 2026-08-02 18:36 UTCVendor advisory
  73. 2026-08-02 18:36 UTCGHSA enrichment
  74. 2026-08-02 07:43 UTCEG score recompute
  75. 2026-08-02 07:43 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-10846?
CVE-2026-10846 is a high vulnerability published on June 10, 2026. 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…
When was CVE-2026-10846 disclosed?
CVE-2026-10846 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10846 actively exploited?
CVE-2026-10846 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-10846?
CVE-2026-10846 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10846?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10846, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10846

Explore →

Is Your Infrastructure Affected by CVE-2026-10846?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.