Zero-Day in End-of-Life D-Link Routers Actively Exploited; No Patch Will Be Released

Unpatched Zero-Day Vulnerability (CVE-2026-0625) in Discontinued D-Link Routers Under Active Attack

CRITICAL
January 8, 2026
4m read
VulnerabilityCyberattackIoT Security

Related Entities

Organizations

Other

DNSChanger

CVE Identifiers

CVE-2026-0625
CRITICAL
CVSS:9.3

Full Report

Executive Summary

A critical zero-day command injection vulnerability, CVE-2026-0625, is being actively exploited in multiple discontinued D-Link DSL routers. The flaw carries a CVSS score of 9.3 and allows for unauthenticated remote code execution (RCE). Threat actors are leveraging this vulnerability to execute arbitrary shell commands on affected devices. D-Link has confirmed the issue but has stated that no patches will be released because the impacted models have reached their end-of-life (EOL). Security researchers and D-Link are urging all users of the affected routers to immediately decommission and replace them to prevent their networks from being compromised.

Vulnerability Details

The vulnerability is an OS command injection flaw located in the dnscfg.cgi Common Gateway Interface (CGI) script. This script is part of the router's web-based management interface and is responsible for processing DNS configuration changes. The script fails to properly sanitize or validate user-supplied input before passing it to a system command. A remote, unauthenticated attacker can craft a malicious HTTP request to this endpoint, injecting arbitrary shell commands that will be executed on the router's underlying operating system with root privileges.

Affected Systems

While D-Link is still conducting a full firmware review, the following models are known or suspected to be vulnerable:

  • DSL-2740R
  • DSL-2640B
  • DSL-2780B
  • DSL-526B
  • Other discontinued DSL gateway models.

Exploitation Status

This is a zero-day vulnerability with confirmed active exploitation in the wild. The Shadowserver Foundation has observed exploitation attempts dating back to at least late November 2025. The attacks are consistent with "DNSChanger" campaigns, where attackers modify the router's DNS settings to redirect user traffic to malicious sites for phishing, ad-fraud, or malware delivery. The vulnerability was reported to D-Link on December 16, 2025, by researchers at VulnCheck who had also observed live exploitation.

Technical Analysis

The exploit is straightforward for an attacker to execute. They simply need to send a crafted request to the vulnerable endpoint. For example:

GET /dnscfg.cgi?service_name=wan&ifname=br0&dns_server_ip=8.8.8.8;`[malicious_command]`

The router's firmware concatenates the dns_server_ip parameter into a shell command without validation, allowing the backticks and the enclosed command to be executed by the system. Compromised routers can be absorbed into botnets for DDoS attacks, used as proxies for further malicious activity, or leveraged to intercept and manipulate the owner's internet traffic.

MITRE ATT&CK Mapping

Impact Assessment

The impact of this vulnerability is high for any individual or small business still using these EOL devices. A successful exploit grants an attacker full control over the router, which is the gateway to the local network. Potential consequences include:

  • Traffic Interception: Attackers can perform man-in-the-middle attacks, stealing credentials, session cookies, and other sensitive data.
  • Phishing and Malware Delivery: By controlling DNS, attackers can redirect users to fake websites for credential harvesting or to sites that deliver malware.
  • Botnet Enlistment: The compromised router can be used as part of a larger botnet to conduct DDoS attacks or send spam.
  • Internal Network Pivoting: An attacker could use the compromised router to scan and attack other devices on the local network.

Since no patch will be provided, these devices will remain perpetually vulnerable.

Cyber Observables for Detection

Type Value Description
url_pattern /dnscfg.cgi Monitor for any access attempts to this CGI script, especially from external IP addresses.
network_traffic_pattern dns_server_ip= Look for suspicious shell commands embedded within the dns_server_ip parameter in GET requests.
dns_query * Monitor for outbound DNS queries to unexpected or known malicious DNS servers from the router itself.

Mitigation

There is no patch for this vulnerability. The only effective mitigation is to immediately disconnect, retire, and replace any affected D-Link router.

  1. Identify Affected Devices: All organizations and individuals should audit their network hardware to identify if any of the vulnerable D-Link models are in use.
  2. Decommission: Immediately disconnect any identified vulnerable router from the internet.
  3. Replace: Replace the EOL device with a modern, supported router from a reputable vendor that provides regular security updates.
  4. Network Segmentation: As a general best practice, do not expose the management interface of any router or network device to the public internet. Access should be restricted to the internal LAN only. This is a core principle of D3FEND's D3-NI - Network Isolation.

Timeline of Events

1
November 20, 2025
Exploitation of CVE-2026-0625 is observed in the wild by Shadowserver.
2
December 16, 2025
VulnCheck reports the zero-day vulnerability to D-Link after observing active exploitation.
3
January 7, 2026
The vulnerability is publicly disclosed, and D-Link confirms no patch will be released.
4
January 8, 2026
This article was published

MITRE ATT&CK Mitigations

The most effective mitigation, short of replacement, is to ensure the router's management interface is not exposed to the internet.

Mapped D3FEND Techniques:

While no patch is available for the affected devices, replacing them with supported hardware that receives updates is the ultimate solution.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

The primary and only viable mitigation strategy for the unpatchable CVE-2026-0625 is device replacement. However, as a general security principle, organizations should implement network isolation for all edge device management interfaces. Configure firewall rules to block any inbound traffic from the internet to the router's web administration port (typically TCP 80 or 443). Access to the management interface should only be permitted from a trusted internal management network or specific IP addresses on the LAN. This practice, while not a fix for the vulnerability itself, prevents external, unauthenticated attackers from reaching the vulnerable dnscfg.cgi endpoint, thereby mitigating the immediate threat of remote exploitation. This should be standard policy for all network infrastructure.

To detect potential compromise of these D-Link routers, security teams should actively monitor DNS traffic originating from the router itself. Establish a baseline of legitimate DNS servers used in your environment (e.g., your ISP's servers or public resolvers like 8.8.8.8). Use a SIEM or network monitoring tool to generate alerts if the router begins sending DNS queries to unauthorized or suspicious servers. This is a key indicator of a 'DNSChanger' style attack. Additionally, create alerts for any HTTP GET requests from the internet targeting the /dnscfg.cgi URI path, as this is a direct sign of an exploitation attempt against this specific vulnerability.

Sources & References

Attackers Exploit Zero-Day in End-of-Life D-Link Routers
Dark Reading (darkreading.com) January 7, 2026
Hackers Exploit Zero-Day in Discontinued D-Link Devices
SecurityWeek (securityweek.com) January 7, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Zero-DayRCED-LinkCVE-2026-0625EOLUnpatchedDNSChangerIoT

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading