CVE-2026-52863 json
Memory corruption could lead to crash and denial of service
published 2026-07-22 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-47677
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- NLnet Labs Unbound 1.25.2
- unbound Debian 13 1.26.1-0+deb13u1
- unbound Debian 14 1.25.2-1
debian advisories DEBIAN-CVE-2026-52863
- unbound hummingbird 1 1.25.2-0.1.hum1
- unbound-libs hummingbird 1 1.25.2-0.1.hum1
- unbound-munin hummingbird 1 1.25.2-0.1.hum1
- unbound-utils hummingbird 1 1.25.2-0.1.hum1
- unbound-anchor hummingbird 1 1.25.2-0.1.hum1
- unbound-dracut hummingbird 1 1.25.2-0.1.hum1
- python3-unbound hummingbird 1 1.25.2-0.1.hum1
red hat advisories RHSA-2026:43588
- unbound openSUSE Tumbleweed 1.25.2-1.1
opensuse advisories openSUSE-SU-2026:11380-1
- unbound Alpine 3.24, Alpine 3.23, Alpine 3.22 1.25.2-r0
alpine advisories ALPINE-CVE-2026-52863
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-52863 updated cvss 5.9
unbound: Unbound: Denial of service due to memory corruption under specific configurations.
-
Red Hat Hardened Images unbound 1.25.2-0.1.hum1, unbound-libs 1.25.2-0.1.hum1, unbound-munin 1.25.2-0.1.hum1, unbound-utils 1.25.2-0.1.hum1, unbound-anchor 1.25.2-0.1.hum1, unbound-dracut 1.25.2-0.1.hum1, +1 morefixed: vendor fix RHSA-2026:43588
-
Red Hat Enterprise Linux 6 unbound, unbound-libs, unbound-python Red Hat Enterprise Linux 7 unbound, unbound-libs, unbound-python Red Hat Enterprise Linux 8 unbound, unbound-libs, python3-unbound Red Hat Enterprise Linux 9 unbound, unbound-libs, unbound-dracut, python3-unbound Red Hat Enterprise Linux 10 unbound Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- NLnet Labs Unbound
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
nlnetlabs.nl
/downloads/unbound/CVE-2026-52863.txt
vendor-advisory
Sources
- CVE List CVE-2026-52863
- NVD CVE-2026-52863
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.