CVE-2026-50252: Unbound Vulnerability
CVE-2026-50252 is a critical vulnerability in Unbound, published in the National Vulnerability Database (NVD) on July 22, 2026. It carries a CVSS v3.1 base score of 9.3 (Critical). According to its CVSS vector, it can be exploited from an adjacent network, needs no privileges and no user interaction.
What is CVE-2026-50252?
Unbound 1.4.22 to 1.25.1 can expose DNS transactions to cache poisoning due to UDP port misuse.
The NVD description (excerpt) reads:
In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled ('so-reuseport: yes') in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks.
NVD maps this issue to CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data).
Affected versions and packages
NVD's CPE configuration lists these vulnerable version ranges:
- unbound from 1.4.22 before 1.25.2
Based on those ranges, the first versions that are no longer listed as vulnerable include: 1.25.2.
Echo's advisory data tracks 1 package for CVE-2026-50252: libunbound8.
Echo-built fixed versions recorded for this CVE:
- libunbound8: 1.25.1-1+e1, 1.25.2-1+e1
Severity and CVSS score
A score of 9.3 puts CVE-2026-50252 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to how automated patch SLAs reduce enterprise risk.
Impact: what an attacker can do
The CVSS vector rates the impact on confidentiality as none, integrity as high and availability as high. The scope is changed, meaning a successful attack can affect resources beyond the vulnerable component. Exploitation requires no privileges and no user interaction, and the attacker reaches the target from an adjacent network.
What this means in practice depends on how Unbound is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.
Is CVE-2026-50252 being exploited in the wild?
Known exploitation: CISA KEV
No. As of November 4, 2026, CVE-2026-50252 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). KEV only lists vulnerabilities with confirmed exploitation, so absence from the catalog is not proof that nobody is exploiting the flaw.
EPSS score and percentile
The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a CVE will see exploitation activity in the next 30 days. On November 3, 2026, CVE-2026-50252 had an EPSS score of 0.002, which corresponds to a probability of 0.17%. It sits at the 7th percentile, which means it is scored as more likely to be exploited than roughly 6% of scored CVEs, placing it below the median of scored CVEs. EPSS is recalculated daily and is a likelihood estimate, not a confirmation, so read it together with KEV status, exposure and CVSS severity.
Attack vector, complexity, privileges and user interaction
Based on the CVSS v3.1 vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H (source: NVD), this is how an attacker has to approach CVE-2026-50252:
- Attack vector: Adjacent (AV:A): the attacker must be on the same shared network segment as the target, for example the same LAN or wireless range, rather than anywhere on the internet.
- Attack complexity: Low (AC:L): no special conditions are needed, so the attack can be repeated reliably.
- Privileges required: None (PR:N): no account or credentials are needed.
- User interaction: None (UI:N): no action by a user is required.
- Scope: Changed (S:C): a successful attack can affect resources beyond the vulnerable component.
Is there a public proof of concept or exploit?
CISA's SSVC assessment recorded in NVD (dated July 22, 2026) lists the exploitation status as "none", which means there was no evidence of active exploitation and no public proof of concept at that time. None of the references in the NVD record is tagged as an exploit. This reflects NVD and CISA records as of November 4, 2026, and public exploit code can appear at any time.
Practical exposure conditions
- Only systems that run an affected version are exposed. Compare the Unbound versions in your hosts and container images against the vulnerable ranges listed above.
- The vector is adjacent-network, so only attackers on the same network segment as the target can reach the flaw. Internet-facing exposure alone does not create the risk.
- No credentials are needed, so exposure does not depend on how well accounts are protected.
- No user has to click or open anything, so the flaw can be triggered without any user action.
- The scope is changed, so a successful attack can reach beyond the vulnerable component.
- CISA's SSVC assessment marks the issue as not automatable, which means attacks are harder to run at scale.
How to fix CVE-2026-50252
- Inventory. Find every host, container image and base image that includes Unbound, including the packages listed above (libunbound8).
- Upgrade. Upgrade to 1.25.2 or later where NVD lists a fixed release, or to the Echo-built fixed package listed above.
- Rebuild and restart. Rebuild container images and restart the services that load Unbound so the patched code is actually used.
- Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2026-50252.
Interim mitigations if you cannot patch immediately
These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.
- Limit who can run code or log in on hosts that use Unbound, because the attack is not remote according to the CVSS vector.
- Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.
How Echo helps with CVE-2026-50252
Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 1 package (libunbound8) and includes Echo-built fixed versions. Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters. Related Unbound advisories: CVE-2026-82717 and CVE-2026-81642.
Frequently asked questions about CVE-2026-50252
What is CVE-2026-50252?
CVE-2026-50252 is a critical vulnerability in Unbound. Unbound 1.4.22 to 1.25.1 can expose DNS transactions to cache poisoning due to UDP port misuse. It has a CVSS base score of 9.3.
Which versions are affected by CVE-2026-50252?
NVD lists these vulnerable ranges: unbound from 1.4.22 before 1.25.2.
Is CVE-2026-50252 actively exploited?
It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.17%, at the 7th percentile (November 3, 2026). On public exploit code: CISA's SSVC assessment in NVD (dated July 22, 2026) lists no public proof of concept.
How do I fix CVE-2026-50252?
Upgrade to 1.25.2 or later where NVD lists a fixed release, or to the Echo-built fixed package listed above. Then rebuild images, restart affected services and re-scan to confirm the fix.
How severe is CVE-2026-50252?
It is rated Critical with a CVSS base score of 9.3. The vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H means it can be exploited from an adjacent network, with no privileges and no user interaction.
Are there other Unbound vulnerabilities I should patch?
Yes. Echo's advisory data also covers CVE-2026-82717 and CVE-2026-81642. Patch them together to reduce the number of upgrade cycles.