CVE-2026-50252: DNS Cache Poisoning via SO_REUSEPORT Source-Port Entropy Reduction in Unbound
- Vendor
- Nlnet Labs
NLnet Labs Unbound versions 1.4.22 through 1.25.1 inclusive contain a UDP source-port entropy weakness associated with the default-enabled SO_REUSEPORT configuration. At startup, Unbound partitions its outgoing UDP source-port pool into disjoint, approximately equal subsets assigned to worker threads. The kernel deterministically distributes incoming queries among workers using the client source IP address and UDP source port. Because outgoing queries use only the handling worker's port subset, observing their source ports reveals worker assignment. An attacker can learn the mapping between incoming source ports and workers for a fixed source IP address, narrowing the outgoing source-port search space and facilitating DNS cache poisoning.
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.
Successful exploitation weakens the protection provided by UDP source-port randomization and increases the feasibility of injecting forged DNS responses into the resolver cache. Poisoned records can cause clients to receive attacker-selected DNS answers, redirect traffic, or lose access to legitimate services. The weakness does not itself establish arbitrary code execution or direct disclosure of resolver memory.
Mitigation
If you can’t patch tonight, do this now.
Disable SO_REUSEPORT by setting 'so-reuseport: no' in the Unbound configuration where operationally feasible, and apply the configuration change. This removes the deterministic SO_REUSEPORT worker-assignment mechanism exploited to reduce source-port entropy. Use this workaround until vendor security updates can be installed.
Remediation
Patch, then assume compromise.
Install vendor security updates addressing CVE-2026-50252 for Unbound and affected dependent packages. For Debian stable (trixie), upgrade to Unbound 1.26.1-0+deb13u1 or a later security-fixed package. Other distributions provide release-specific updates; an exact upstream first-fixed version is not established.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
Frequently asked questions
- Is CVE-2026-50252 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-50252 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-50252?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-50252.
- Is there a patch for CVE-2026-50252?
- Install vendor security updates addressing CVE-2026-50252 for Unbound and affected dependent packages. For Debian stable (trixie), upgrade to Unbound 1.26.1-0+deb13u1 or a later security-fixed package.
- What products are affected by CVE-2026-50252?
- Nlnet Labs Unbound.
- How severe is CVE-2026-50252?
- CVE-2026-50252 has a CVSS v4 score of 5.7 (Medium) and an EPSS score of 0.17% (7th percentile) as of Nov 17, 2026.
Recent activity
47 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.