CVE-2026-52863

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.25.0 up to and including 1.25.1, a fix that makes the 'respip' and 'dns64' modules work together, creates a shallow copy of the view name in effect that could lead to memory corruption if the owner of the original view name is jostled out when Unbound is under pressure. Unbound needs to be configured with one of 'respip'/'rpz' modules, together with a module that can attach subqueries (respip CNAME redirection, dns64, subnetcache) and a configured 'access-control-view' while Unbound is under pressure so that joslte logic kicks in and starts dropping slow queries. The subquery is getting a shallow copy of the view name and if the super query which owns the view name is jostled out, memory corruption can occur. Likelihood of a crash is low, since it relies heavily on the underlying memory allocator and the memory layout. Debug memory builds (e.g., ASAN) that catch the free terminate the server.

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

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 22, 2026
No patch confirmed yet.

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
unbound1.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 21× in last 7d / 94× 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 191 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52863?
CVE-2026-52863 is a medium vulnerability published on July 22, 2026. In NLnet Labs Unbound 1.25.0 up to and including 1.25.1, a fix that makes the 'respip' and 'dns64' modules work together, creates a shallow copy of the view name in effect that could lead to memory corruption if the owner of the original view name is jostled out when Unbound is under pressure.…
When was CVE-2026-52863 disclosed?
CVE-2026-52863 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-52863 actively exploited?
CVE-2026-52863 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 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-52863?
CVE-2026-52863 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-52863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52863, 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-52863

Explore →

Is Your Infrastructure Affected by CVE-2026-52863?

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