CVE-2026-50046

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-47672 (ENISA EUVD) · GHSA-fg9v-m7xf-p865 (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.9Exploit: None knownExposed services: Not assessed

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 22, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
Patch available.
Web page
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 / EcosystemFix (by version range) / 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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.15.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.15.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.15.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.13.1-1 ... 1.25.2-1 (47 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.17.1-2 ... 1.26.1-1 (26 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2 ... 1.26.0-2 (15 versions)
  • every version up to 1.26.1-0+deb13u1: fixed in 1.26.1-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
unbound1.22.0-2 ... 1.25.1-1 (9 versions)
  • every version up to 1.25.2-1: fixed in 1.25.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 257 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-50046?
CVE-2026-50046 is a medium-severity vulnerability; its CVE record was 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 ('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…
When was CVE-2026-50046 made public?
CVE-2026-50046 was made public on July 22, 2026: that is the date its CVE record's CNA, NLnet Labs, gives for when the vulnerability was made public. The CVE record itself was published on July 22, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-50046 actively exploited?
CVE-2026-50046 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50046?
CVE-2026-50046 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50046?
A fix for CVE-2026-50046 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50046 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs