Skip to content
Noroxi
CVE-2026-52863· NVD / CVE Program· CNA NLnet Labs

Memory corruption could lead to crash and denial of service

Noroxi assessment

Priority: Monitor (action score 23/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: NLnet Labs Unbound 1.25.2; azl3 unbound 1.25.1-1 on Azure Linux 3.0 1.25.2-1.

Low priority for now. Upgrade to NLnet Labs Unbound 1.25.2; azl3 unbound 1.25.1-1 on Azure Linux 3.0 1.25.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.9 · v3.1—No exploit Fix available
Published
Jul 22, 2026
Updated
Jul 24, 2026
EPSS
0.3% · 28th percentile

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · NLnet Labs
5.9
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-52863

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nlnetlabs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nlnetlabsunbound

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nlnetlabs unbound1.25.0 and later · before 1.25.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (NLnet Labs). Independent of NVD's CPE analysis and usually ahead of it.

  • NLnet Labs Unbound

    • 1.25.0 and later · before 1.25.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.22unboundfrom 1.25.0 · before 1.25.2-r01.25.2-r0
Debian:12unboundall versions—
Debian:13unboundbefore 1.26.1-0+deb13u11.26.1-0+deb13u1
Debian:14unboundbefore 1.25.2-11.25.2-1
openSUSE:Tumbleweedunboundbefore 1.25.2-1.11.25.2-1.1
Red Hat:hummingbird:1python3-unboundbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unboundbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-anchorbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-develbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-dracutbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-libsbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-muninbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1
Red Hat:hummingbird:1unbound-utilsbefore 0:1.25.2-0.1.hum10:1.25.2-0.1.hum1

Same product

nlnetlabs: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-25042Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy.
    40Plan
  • CVE-2019-25039Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c.
    40Plan
  • CVE-2019-25038Unbound before 1.9.5 allows an integer overflow in a size calculation in dnscrypt/dnscrypt.c.
    40Plan
  • CVE-2019-25035Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.
    40Plan
  • CVE-2019-25034Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading to an out-of-bounds write.
    40Plan
  • CVE-2019-25033Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NLnet Labs Unbound1.25.2Vendor (CNA)
azl3 unbound 1.25.1-1 on Azure Linux 3.01.25.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:unbound1.25.2-r0 · Alpine:v3.22Package registry (OSV)
debian:unbound1.26.1-0+deb13u1 · Debian:13Package registry (OSV)
opensuse:unbound1.25.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:python3-unbound0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-anchor0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-devel0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-dracut0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-libs0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-munin0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:unbound-utils0:1.25.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-3327863 days apartPossible arbitrary code execution during DNSSEC validation
    36Monitor
  • CVE-2026-7822756 days apartUse-after-free in DoQ stream output buffer on reset re-transmission
    26Monitor
  • CVE-2026-500460 days apartPossible heap use-after-free in an error path when a DoT forwarded query is jostled out
    23Monitor
  • CVE-2026-8272056 days apartUse-after-free in DoH stream cleanup code path
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records