Skip to main content
Mallory
MediumVulnerability

CVE-2026-50045: Unbound Upstream Amplification Quota Bypass via DNSSEC Validation Restarts

Published Jul 22, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS5.3Medium · v3.1
EPSS0.46%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Nlnet Labs
IdentifiersCVE-2026-50045CWE-770

NLnet Labs Unbound versions 1.22.0 through 1.25.1 contain an upstream-query quota bypass caused by DNSSEC validation restarts resetting max-global-quota accounting. A single client query for a deeply nested name beneath a DNSSEC-signed parent can cause the resolver to send more upstream packets than the configured per-query quota permits, bypassing a security control intended to limit upstream traffic amplification.

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 attacker can induce upstream DNS traffic beyond the configured amplification limit, increasing network traffic and resolver or upstream-server resource consumption. This can contribute to service degradation or denial of service. The vulnerability is rated Medium severity; it does not establish code execution, cache poisoning, or confidentiality loss.

Mitigation

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

No vulnerability-specific interim workaround is identified. Restricting recursive-query access to trusted clients and enforcing independent traffic limits can reduce exposure and amplification impact, but do not repair the quota-accounting flaw.

Remediation

Patch, then assume compromise.

Upgrade Unbound to version 1.25.2 or a later supported release containing the fix. For Debian 13 (trixie), install version 1.26.1-0+deb13u1 or later through the security updates. For Rocky Linux deployments, apply the applicable Unbound security package updates associated with advisories crlsa-2026_97121 or crlsa-2026_97497.

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-50045 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-50045 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-50045?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-50045.
Is there a patch for CVE-2026-50045?
Upgrade Unbound to version 1.25.2 or a later supported release containing the fix. For Debian 13 (trixie), install version 1.26.1-0+deb13u1 or later through the security updates.
What products are affected by CVE-2026-50045?
Nlnet Labs Unbound.
How severe is CVE-2026-50045?
CVE-2026-50045 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.46% (41st percentile) as of Nov 14, 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 activity3Community discussion across Reddit, Mastodon, and other social sources.