On this page (7 sections)
A critical flaw has been recorded in the D-Link DIR-600L router running firmware 2.17b02. According to the GitHub Advisory Database entry, the hnap_main function in the HNAP handler can be driven into a stack-based buffer overflow, the attack can be carried out remotely, and an exploit has been published.
If you run a DIR-600L at an office, a branch, a home office or a client site, treat this as urgent. The records do not describe a fix, so the practical goal for now is to limit who can reach the router's management and HNAP services.
What happened
The vulnerability was published to the National Vulnerability Database and the GitHub Advisory Database on Nov 15, 2026. The description says the flaw sits in the function hnap_main of the file htdocs/cgibin, part of the HNAP Handler component of the DIR-600L. A crafted manipulation leads to a stack-based buffer overflow, and the attack can be launched remotely.
The GitHub entry is marked unreviewed, lists no package, and shows both affected and patched versions as unknown. The NVD page repeats the same description, so it is not independent confirmation. The advisory's reference list includes a write-up in a third-party advisories repository, VulDB entries and the D-Link homepage, but the research does not include a D-Link security bulletin or firmware release for this issue.
Technical details in plain terms
A stack-based buffer overflow happens when a program copies more data into a fixed-size memory area on the call stack than it can hold. The extra data overwrites neighboring memory, which can crash the program or, in the worst cases, let an attacker change what code runs. On a router, the vulnerable program usually runs with high privileges, so a successful attack can mean control of the device.
HNAP (Home Network Administration Protocol) is a SOAP-based protocol some D-Link routers use for management and configuration over HTTP. The advisory's CVSS v4 metrics on the GitHub entry describe network attack vector, low complexity, no attack requirements, no privileges and no user interaction, with high impact on confidentiality, integrity and availability. In short, the scoring assumes an attacker needs no login and no help from a user.
The two scores differ: the CVE record shows 10 while the GitHub page shows 9.3 under CVSS v4. Both are in the critical range, and the gap does not change the advice.
Who is affected
The advisory names D-Link DIR-600L firmware 2.17b02. It does not say whether other firmware versions or other models share the same HNAP code, so do not assume other versions are safe. Check your own device rather than relying on the version alone.
Realistic exposure depends on where the HNAP service can be reached. A router whose web management is reachable from the internet is at greater risk than one reachable only from the local network. A local-only device is still exposed to anything already on your LAN, such as a compromised laptop or a guest on Wi-Fi.
How to check your exposure
- Log in to the router's admin page from inside your network and find the model name and firmware version, usually on a status or firmware page. Confirm whether it is a DIR-600L on 2.17b02.
- Check whether remote management (web administration from the WAN) is enabled and turn it off if you do not need it.
- From a machine outside your network, such as a mobile connection, confirm the router's admin interface does not answer on your public IP address.
- Review port forwarding and UPnP rules for anything that exposes the router itself or internal services you do not recognize.
You can also review what your public address exposes. A read-only external scan of a site you control can show open services; see Webforta Scan for scans of websites you verify. It will not tell you whether a given router firmware is vulnerable.
What to do now
The research does not document a patch, so these steps focus on reducing exposure and planning for replacement.
- Identify every D-Link DIR-600L in use, including devices at home offices and client sites, and note the firmware version.
- Disable remote (WAN-side) administration and any HNAP or management access from the internet.
- Restrict management access to a single trusted wired machine or a dedicated management VLAN where the router supports it.
- Check the D-Link support site for a security notice or newer firmware for the DIR-600L, and install it only if D-Link lists it as addressing this issue.
- If no fix is offered and the device is end of support, plan to replace it with a model that still receives security updates.
- Change the router admin password and Wi-Fi keys if you suspect the device was reachable from the internet while vulnerable.
- Put the router behind another firewalled device where possible, so its management interface is not directly exposed.
Detection and monitoring
Consumer routers keep little useful logging, so signs of compromise are often indirect. Watch for unexpected changes to DNS settings, new port forwards, admin password resets, unexplained reboots, slow connections, or devices on your network contacting unfamiliar hosts.
- Compare the router's DNS servers and port-forwarding table against your known-good configuration.
- Check whether your public IP now answers on ports it did not before.
- For business sites behind the router, monitor uptime, TLS certificates and DNS records so unexpected changes are noticed quickly. Webforta Monitor covers uptime, certificate, DNS and header-change monitoring.
- Run a free SSL certificate check on your public sites if you suspect traffic interception.
If you believe a router was taken over, follow the steps in Website hacked: what to do, and consider resetting the device to factory defaults before reconfiguring it with a new password. For broader habits that limit the damage from a single weak device, see small business website security.
What is still unknown
- Whether D-Link has acknowledged the issue or released fixed firmware.
- Which other firmware versions or models, if any, are affected.
- Whether the published exploit is being used in real attacks. The description says it may be used, but no source confirms exploitation.
- Which party assigned the CVSS 10 score on the CVE record.
We will treat this as an evolving story. Until a vendor statement or fixed version appears, assume a DIR-600L on 2.17b02 is vulnerable and keep it off the public internet.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
