CVE-2026-10846

HIGHNVD 7.57.5
EchelonGraph scoreHIGH 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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(high)
EPSS
4.3%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 17, 2026

Vendor Advisories for CVE-2026-10846(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-ldns (1.8.3-2ubuntu0.1~esm1) @ noble2026-07-05ubuntu

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.

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 44× in last 7d / 188× 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 188 total refreshes for this CVE.

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

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 June 17, 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 4.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.