Skip to main content
Mallory
HighVulnerability

CVE-2026-81634: Heap Buffer Overflow in Unbound RRSet Canonicalisation

Published Sep 16, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days13 mentions · peak 4 in a dayToday
CVSS7.5High · v3.1
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-81634CWE-122 · Heap-based Buffer Overflow

CVE-2026-81634 is a heap buffer overflow in NLnet Labs Unbound through version 1.26.0. The RRSet canonicalisation routine omits the first owner name from a buffer-length check. Processing a 255-byte query name together with a large TCP DNS response can consequently overflow a heap buffer. An attacker controlling a malicious nameserver or able to tamper with an incoming response can trigger the flaw before DNSSEC validation, potentially crashing the resolver.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote, unauthenticated exploitation can corrupt heap memory and crash Unbound, disrupting DNS resolution. The CNA assessment identifies high availability impact without confidentiality or integrity impact. SUSE assesses potential confidentiality and integrity impacts as well, but arbitrary code execution is not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No vendor-confirmed workaround is documented. DNSSEC validation alone does not prevent exploitation because the vulnerable processing occurs first. If patching is delayed, consider temporarily replacing or isolating the resolver and restricting upstream DNS communication to trusted services where operationally feasible. Protecting DNS transport against tampering reduces one attack route but does not address malicious nameservers.

Remediation

Patch, then assume compromise.

Upgrade Unbound to version 1.26.1 or a later fixed release, or install the applicable distribution security update containing a backported fix. Debian trixie provides the fix in version 1.26.1-0+deb13u1. Assess distribution packages using their complete package release identifiers rather than upstream version numbers alone. Where updates remain pending or the product is unsupported, migrate to a supported, patched resolver.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Nlnet LabsUnboundapplication
FAQ

Frequently asked questions

Is CVE-2026-81634 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-81634 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-81634?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-81634.
Is there a patch for CVE-2026-81634?
Upgrade Unbound to version 1.26.1 or a later fixed release, or install the applicable distribution security update containing a backported fix. Debian trixie provides the fix in version 1.26.1-0+deb13u1.
What products are affected by CVE-2026-81634?
Nlnet Labs Unbound.
How severe is CVE-2026-81634?
CVE-2026-81634 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.48% (42nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

51 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+43 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.