Skip to main content
Mallory
CriticalVulnerability

CVE-2026-81642: DNSKEY Digest Buffer Overflow in NLnet Labs Unbound

Published Sep 16, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days18 mentions · peak 4 in a dayToday
CVSS9.1Critical · v4
EPSS0.96%62nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-81642CWE-122 · Heap-based Buffer Overflow

CVE-2026-81642 is a buffer overflow in the DNSSEC validator of NLnet Labs Unbound through version 1.26.0. During DNSKEY digest processing, a crafted DNSKEY whose owner-name compression pointer references its own RDATA can overflow the digest buffer. An attacker controlling a malicious DNS zone can trigger the vulnerability by querying a vulnerable resolver for that zone, causing denial of service and potentially remote code execution through attacker-controlled data.

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.

Exploitation can corrupt resolver memory and cause a crash, disrupting DNS resolution for dependent clients. Successful exploitation may also permit arbitrary code execution in the Unbound process context, potentially compromising the confidentiality, integrity, and availability of resources accessible to that process. Remote code execution is a potential outcome, not an established result of every trigger.

Mitigation

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

No vulnerability-specific vendor workaround is documented. Pending patching, restrict recursive DNS service to authorized clients and trusted networks, and limit resolution of untrusted zones where operationally feasible. These measures reduce exposure but do not eliminate the vulnerability, because permitted clients can still cause resolution of malicious DNS data.

Remediation

Patch, then assume compromise.

Upgrade Unbound to version 1.26.1 or a later security-fixed release, or install the distribution's package update addressing CVE-2026-81642. The fix checks digest-buffer capacity after decompression and before writing. For installations that cannot immediately upgrade, NLnet Labs provides two manual patches tested against Unbound 1.26.0: a vulnerability-only fix and an alternative including additional code improvements. Identified distribution fixes include Photon OS package version 1.26.1-1.ph5 and Debian trixie version 1.26.1-0+deb13u1.

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-81642 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-81642 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-81642?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-81642.
Is there a patch for CVE-2026-81642?
Upgrade Unbound to version 1.26.1 or a later security-fixed release, or install the distribution's package update addressing CVE-2026-81642. The fix checks digest-buffer capacity after decompression and before writing.
What products are affected by CVE-2026-81642?
Nlnet Labs Unbound.
How severe is CVE-2026-81642?
CVE-2026-81642 has a CVSS v4 score of 9.1 (Critical) and an EPSS score of 0.96% (62nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
+65 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 activity21Community discussion across Reddit, Mastodon, and other social sources.