PatchSiren cyber security CVE debrief
CVE-2026-52863 NLnet Labs CVE debrief
A memory corruption vulnerability exists in Unbound 1.25.0-1.25.1. The issue arises from a shallow copy of the view name in effect, which could lead to memory corruption if the owner of the original view name is jostled out when Unbound is under pressure. This vulnerability requires specific configurations, including 'respip'/'rpz' modules, 'access-control-view', and subquery modules like 'respip CNAME redirection', 'dns64', or 'subnetcache'. The likelihood of a crash is low due to the specific conditions required for exploitation.
- Vendor
- NLnet Labs
- Product
- Unbound
- CVSS
- MEDIUM 5.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-22
- Original CVE updated
- 2026-07-22
- Advisory published
- 2026-07-22
- Advisory updated
- 2026-07-22
Who should care
Users of Unbound 1.25.0-1.25.1, particularly those with configured 'respip'/'rpz' modules, 'access-control-view', and subquery modules like 'respip CNAME redirection', 'dns64', or 'subnetcache', should be aware of this vulnerability. Operators, platform administrators, vulnerability management teams, and security teams should review Unbound configurations and monitor for potential issues under heavy load.
Technical summary
The vulnerability occurs when Unbound is configured with specific modules and is under pressure, causing the jostle logic to drop slow queries. If the super query owning the view name is jostled out, memory corruption can occur due to a shallow copy of the view name in the subquery. The likelihood of a crash is low, as it heavily relies on the underlying memory allocator and memory layout. Affected configurations include 'respip'/'rpz' modules, 'access-control-view', and subquery modules like 'respip CNAME redirection', 'dns64', or 'subnetcache'.
Defensive priority
Medium priority due to the specific conditions required for exploitation and the low likelihood of a crash. However, given the potential impact, it is essential to review and adjust Unbound configurations to minimize the risk of exploitation and monitor for potential issues under heavy load.
Recommended defensive actions
- Update to a version of Unbound that addresses this vulnerability.
- Review and adjust Unbound configurations to minimize the risk of exploitation.
- Monitor for potential issues with Unbound under heavy load.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record was published on 2026-07-22T14:17:20.757Z and has not been modified since then. The NVD entry is currently Undergoing Analysis. This vulnerability affects Unbound versions 1.25.0 and 1.25.1, specifically when configured with 'respip'/'rpz' modules, 'access-control-view', and subquery modules like 'respip CNAME redirection', 'dns64', or 'subnetcache'. Defenders should verify Unbound configurations and monitor for potential issues under heavy load.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-52863 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-52863
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-52863 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-52863
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-52863.txt
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.