CVE-2025-71058 dhcp-dns-server CVE debrief

Who should care

Network administrators and security teams responsible for managing DNS infrastructure, particularly those using Dual DHCP DNS Server 8.01, should be aware of this vulnerability. The critical severity (CVSS score of 9.1) indicates a high risk of exploitation, which could lead to DNS cache poisoning and potential redirection of users to malicious sites.

Technical summary

The Dual DHCP DNS Server 8.01 implementation fails to validate the origin of UDP DNS responses. It matches responses primarily by TXID and caches them without ensuring they come from a legitimate upstream DNS server. This flaw allows remote attackers to inject forged responses, potentially poisoning the DNS cache and redirecting users to attacker-controlled destinations. The vulnerability's impact is critical, with a CVSS score of 9.1, indicating a high risk of exploitation. Network administrators and security teams should prioritize patching or mitigating this vulnerability to prevent potential DNS cache poisoning and redirection of users to malicious sites. The attack vector is network-based, requires low attack complexity, and no user interaction. The high impact on integrity and availability further emphasizes the need for swift action. Limited source detail is available, and further investigation is needed to fully understand the vulnerability's impact and scope.

Defensive priority

High priority should be given to patching or mitigating this vulnerability, as the attack vector is network-based (AV:N), requires low attack complexity (AC:L), and no user interaction (UI:N). The high impact on integrity (I:H) and availability (A:H) further emphasizes the need for swift action.

Recommended defensive actions

• Apply the vendor patch or update to a fixed version of Dual DHCP DNS Server as soon as available.
• Implement additional monitoring and logging to detect potential DNS cache poisoning attempts.
• Consider using DNSSEC or other DNS security measures to enhance the security of DNS infrastructure.
• Restrict access to DNS servers to only trusted sources, if possible.
• Regularly review and update the configuration of DNS servers to ensure they are properly secured.

Evidence notes

The CVE record was published on 2026-04-07T19:16:43.220Z and last modified on 2026-07-24T22:10:00.140Z. The NVD entry is currently awaiting analysis. Limited source detail is available, and further investigation is needed to fully understand the vulnerability's impact and scope.

Official resources