CVE-2026-50046

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-07-22. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('serviced_query') lifetime but also referenced by another struct ('waiting_tcp'). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound's configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured '#authname' suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic
https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50046.txt

Vendor Advisories for CVE-2026-50046(3)

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
redhatunbound-main-1.25.2-0.1.hum12026-07-22redhat

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

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
unbound—1.25.2-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
unbound1.17.1-2 ... 1.26.0-2 (25 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
unbound1.22.0-2 ... 1.25.1-1 (9 versions)1.25.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 83× 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 186 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50046?
CVE-2026-50046 is a medium vulnerability published on July 22, 2026. In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('servicedquery') lifetime but also referenced by another struct ('waitingtcp'). When the owning struct is jostled out of the mesh while the DoT TCP…
When was CVE-2026-50046 disclosed?
CVE-2026-50046 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50046 actively exploited?
CVE-2026-50046 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 84.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50046?
CVE-2026-50046 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-50046?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50046, 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-50046

Explore →

Is Your Infrastructure Affected by CVE-2026-50046?

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

Start Free Scan →Browse All CVEs