On this page (8 sections)
A stack-based buffer overflow has been recorded in the DrayTek Vigor2960 router, affecting firmware up to and including 1.5.1.6. According to the NVD entry for CVE-2026-132142, the flaw can be triggered remotely and an exploit has been published. Upgrading to firmware 1.5.1.7 mitigates it.
If your office, store, or hosting setup uses a Vigor2960 as its edge router or VPN gateway, this is worth handling promptly. The record comes from a single source so far, so some details below are marked as unconfirmed.
What happened
The vulnerability was published on 2026-11-18. NVD describes it as a flaw in the function dataflowstatus of the file /cgi-bin/mainfunction.cgi, part of the CGI process on the device. Manipulating the argument named option causes a stack-based buffer overflow, and the attack can be started remotely.
The record states that the exploit has been published and may be used. It does not say that attacks are happening, and the research does not list the CVE in CISA's Known Exploited Vulnerabilities catalog. Treat it as publicly exploitable in principle, with active abuse unconfirmed.
Technical details in plain terms
A stack-based buffer overflow happens when a program copies more data into a fixed-size memory area than it can hold, overwriting neighboring memory. On network devices this class of bug often leads to a crash (the router reboots or drops traffic) and, depending on the memory protections in place, can sometimes allow an attacker to run their own code. The NVD text does not state which of these outcomes applies here, so no impact beyond the weakness class should be assumed.
The vulnerable code sits in the router's web management CGI, which is the same interface administrators use in a browser. That makes the management interface exposure the key factor in how reachable the bug is.
Vendor position
The NVD entry quotes the vendor as saying that 1.5.1.6 is not the latest version for the 2960, that the latest version fixes many security issues, and that another release is planned that should address the reported issues. In practice this means 1.5.1.7 is the version the record points to now, and a further release may follow. Check DrayTek's firmware page for the newest build rather than stopping at 1.5.1.7 if a later one is available.
The firmware package is referenced from the DrayTek download server. The record also links to a VulDB entry and a public analysis repository. These appear to derive from the same disclosure, so they are not independent confirmation.
Who is affected
- Organizations running a DrayTek Vigor2960 on firmware 1.5.1.6 or any earlier version.
- Setups where the router's web management interface is reachable from the internet, or from untrusted internal networks such as guest Wi-Fi or shared hosting segments.
- Sites and stores that depend on that router for connectivity, VPN access to servers, or office-to-hosting tunnels, since a crash or takeover of the gateway affects everything behind it.
Other DrayTek models are not named in the record. Because the vendor says 1.5.1.6 is behind the latest release and that the latest version fixes many security issues, it makes sense to bring the device fully up to date rather than treating this as a single isolated fix.
How to check your exposure
First confirm the model and firmware version in the router's administration interface (the system status or dashboard page normally shows it). Anything at 1.5.1.6 or lower is in scope.
Then check whether the management interface answers from the internet. From a machine outside your network, request the router's public address and see whether a login page or any web response comes back. This read-only check shows the response headers only; replace the placeholder with your own public IP or hostname.
curl -I --max-time 10 https://ROUTER_PUBLIC_IP_OR_HOSTNAME/A timeout or refused connection from outside is the result you want. If you get a response, the interface is exposed and should be restricted as described below.
What to do now
- Identify every Vigor2960 you manage and record its current firmware version.
- Download firmware 1.5.1.7 (or a newer release if DrayTek has published one) from DrayTek's official site and verify you are on the vendor domain.
- Back up the router configuration before upgrading.
- Schedule a short maintenance window, apply the firmware, and confirm the new version in the admin interface afterwards.
- Disable remote management from the WAN side unless you truly need it; if you do, restrict it to specific trusted IP addresses or a VPN.
- Limit management access on the LAN to an admin network or specific hosts, and use strong unique admin credentials.
- Review router logs and admin accounts after the upgrade for anything unfamiliar, and watch for a further DrayTek release as the vendor indicated.
Detection and monitoring
Because the bug may cause crashes, unexplained router reboots, dropped tunnels, or management-interface errors are worth investigating, especially if they began around the time the exploit became public. Keep router logs on a separate syslog host if possible so they survive a reboot.
Outside-in checks help too. Webforta Monitor can watch uptime and certificate or DNS changes for the services behind your gateway, which can flag an outage or unexpected change early. For general guidance on spotting compromise, see how to check if a website is hacked. None of this replaces patching the router itself.
What is still unknown
- Whether authentication is required to reach the vulnerable function (the description is silent; a reference title suggests it may be).
- Whether the flaw allows code execution or only a crash.
- Whether attackers are exploiting it in the wild.
- What the next planned DrayTek release will contain.
This article will be most reliable once DrayTek publishes its own advisory or a second source confirms details. Until then, the safe course is the same either way: upgrade and reduce exposure.
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.
