CVE-2026-52863

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-47677 (ENISA EUVD) · GHSA-5gh2-8ch2-g46c (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: None knownExposed services: Not assessed

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.9MEDIUMmedium confidence
EG Risk
42
EG Risk 42/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.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
30th
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.4% 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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.

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.25.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.25.0 up to 1.25.2-r0: fixed in 1.25.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
unbound—
  • 1.25.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 8× in last 7d / 48× 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 270 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 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-52863?
CVE-2026-52863 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-52863 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-52863 actively exploited?
CVE-2026-52863 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52863?
CVE-2026-52863 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-52863?
A fix for CVE-2026-52863 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52863 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-52863

Explore →

Is Your Infrastructure Affected by CVE-2026-52863?

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