Skip to main content
Mallory
HighVulnerability

CVE-2026-82717: Heap Buffer Overflow in Unbound CNAME Synthesis

Published Sep 16, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 4 in a dayToday
CVSS8.4High · v4
EPSS0.78%57th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-82717CWE-122 · Heap-based Buffer Overflow

CVE-2026-82717 is a heap buffer overflow in NLnet Labs Unbound through version 1.26.0. During CNAME synthesis while processing an upstream DNS response, enforcing a maximum TTL rewrites a value in the packet buffer. A crafted DNS compression pointer referencing that overwritten value can invalidate a domain name and trigger an error path that fails to advance the buffer position correctly. Subsequent processing can progressively corrupt heap memory, eventually crashing the resolver. Remote code execution is possible on particular systems and compilation configurations, depending heavily on heap memory layout.

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.

An unauthenticated remote attacker can cause heap corruption and resolver crashes, disrupting DNS resolution. On susceptible systems, the corruption may permit arbitrary code execution in the affected process's security context, potentially compromising confidentiality, integrity, and availability. Reliable code execution depends on heap layout, system characteristics, and compilation options; it is not an assured outcome on every affected installation.

Mitigation

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

No validated vulnerability-specific workaround is documented. Pending patching, reduce resolver exposure and monitor for unexpected crashes. Restricting access to trusted clients alone does not eliminate the malicious-upstream-response attack path. Where operationally feasible, temporarily move DNS resolution to a patched alternative resolver.

Remediation

Patch, then assume compromise.

Upgrade to Unbound 1.26.1 or a later vendor-supported fixed release, or install the distribution's security-fixed backport. Update affected installed libraries and bindings as well as the resolver package, and restart services or applications using them. Confirm remediation using distribution package versions rather than upstream version numbers alone, because some vendors backport fixes. Identified fixed packages include Photon OS 1.26.1-1.ph5 and Debian trixie 1.26.1-0+deb13u1.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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-82717 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-82717 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-82717?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-82717.
Is there a patch for CVE-2026-82717?
Upgrade to Unbound 1.26.1 or a later vendor-supported fixed release, or install the distribution's security-fixed backport. Update affected installed libraries and bindings as well as the resolver package, and restart services or applications using them.
What products are affected by CVE-2026-82717?
Nlnet Labs Unbound.
How severe is CVE-2026-82717?
CVE-2026-82717 has a CVSS v4 score of 8.4 (High) and an EPSS score of 0.78% (57th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

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