Skip to main content
Mallory
LowVulnerability

CVE-2026-77860: Unbound serve-expired wait-limit bypass

Published Sep 16, 2026 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS3.7Low · v3.1
EPSS0.30%23rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-77860CWE-682

CVE-2026-77860 affects NLnet Labs Unbound versions 1.20.0 through 1.26.0 inclusive. The serve-expired code path incorrectly decrements the per-client-IP wait-limit counter twice, allowing an attacker to bypass a query-accounting countermeasure introduced for DNSBomb (CVE-2024-33655). An attacker controlling an authoritative DNS zone can alternate queries that remain unanswered with queries for expired cached records that receive immediate serve-expired responses. These expired-cache queries, termed pumps, offset the counter increases from unanswered queries, allowing pending requests from one source IP to accumulate up to the global per-thread mesh quota.

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 bypass the per-client pending-query limit and occupy resolver query capacity up to num-queries-per-thread, potentially degrading DNS availability or causing denial of service. The vulnerability can contribute to a pulsing DNS amplification attack by bypassing one DNSBomb countermeasure. No confidentiality or integrity impact is identified.

Mitigation

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

Disabling serve-expired is a potential temporary mitigation inferred from the vulnerable code path; validate its operational consequences before deployment. Restrict recursive DNS access to authorized clients and networks to reduce exposure. Do not rely on the per-client wait-limit alone, since its accounting can be bypassed. These measures do not replace installing the fix.

Remediation

Patch, then assume compromise.

Upgrade Unbound to version 1.26.1 or a later supported release, or install a distribution security update containing the fix. Debian 13 provides the fix in version 1.26.1-0+deb13u1. Update affected Unbound packages and associated installed libraries or bindings through supported distribution repositories.

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-77860 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-77860 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-77860?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-77860.
Is there a patch for CVE-2026-77860?
Upgrade Unbound to version 1.26.1 or a later supported release, or install a distribution security update containing the fix. Debian 13 provides the fix in version 1.26.1-0+deb13u1.
What products are affected by CVE-2026-77860?
Nlnet Labs Unbound.
How severe is CVE-2026-77860?
CVE-2026-77860 has a CVSS v3.1 score of 3.7 (Low) and an EPSS score of 0.30% (23rd percentile) as of Nov 7, 2026.
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.