On this page (6 sections)
A new vulnerability, CVE-2026-132143, affects DrayTek Vigor2960 firmware up to and including 1.5.1.6. The flaw is a stack-based buffer overflow in the backup handler of the router's web interface. According to the NVD record, it can be launched remotely and the exploit has been disclosed publicly.
If you run a Vigor2960 at an office, a branch or a hosting site, you should check your firmware version and plan an upgrade to 1.5.1.7. The vendor also says a further release is planned, so keep an eye out for it.
What happened
The NVD entry, published on 2026-11-18, describes a flaw in the function doWebBackup of the file /cgi-bin/mainfunction.cgi, part of the Backup Handler component. Manipulating the path/value argument leads to a stack-based buffer overflow. The record states the attack can be launched remotely and that a public exploit exists.
The references include a public security analysis repository whose case name describes the issue as an authenticated stack overflow in doWebBackup. NVD's own description does not say whether authentication is required, so treat that detail as coming from the case title only and not confirmed by NVD.
Technical background
A stack-based buffer overflow happens when a program copies more data into a fixed-size memory area on the stack than it can hold. The excess data overwrites neighboring memory. In the worst case an attacker can crash the service or change how the program executes. The research does not state what impact this specific bug has beyond the overflow itself, so we do not claim code execution here.
The vulnerable code sits in a CGI program that handles the router's web-based backup feature. That means exposure depends mostly on who can reach the router's web management interface.
Who is affected
- Owners of DrayTek Vigor2960 devices running firmware 1.5.1.6 or earlier.
- Teams that expose the router's web administration page to the internet or to large internal networks.
- Agencies and hosting administrators who manage Vigor2960 units for clients.
The research does not cover other Vigor models, so do not assume they are affected or safe based on this record alone.
What to do now
The vendor guidance quoted in the record is that 1.5.1.6 is not the latest firmware for the 2960 and that the latest version fixes many security issues. DrayTek also says another release is planned to address the reported issues, so keep checking for newer firmware after you reach 1.5.1.7.
- Log in to the router and note the current firmware version.
- If it is 1.5.1.6 or earlier, download 1.5.1.7 from DrayTek's firmware page and read the release notes first.
- Export and store a copy of your current configuration somewhere safe before upgrading.
- Schedule the upgrade in a maintenance window and apply it.
- Confirm the new version after reboot and test VPN, routing and WAN failover.
- Restrict access to the web management interface to trusted admin addresses, and turn off remote administration from the internet if you do not need it.
- Check DrayTek's site again for the follow-up release the vendor mentioned.
How to check your exposure
First, identify every Vigor2960 you own, including units at remote sites. Then confirm the firmware version on each one from its admin dashboard. Next, find out from where the web management port can be reached. From a network outside your own, test whether the router's admin page loads. If it does, treat that unit as higher priority.
You can also review your website's public-facing configuration with the free SSL certificate checker and security headers checker, though these will not tell you a router's firmware version.
Detection and monitoring
The research gives no indicators of compromise, so there is no signature to hunt for. Practical steps are limited to watching for the unusual. Review router logs for repeated requests to the backup function in /cgi-bin/mainfunction.cgi, unexpected reboots or crashes of the web service, and configuration changes you did not make. If a device behaves oddly and ran 1.5.1.6 or earlier with exposed management, consider changing admin credentials after upgrading and reviewing its configuration.
Uptime and DNS monitoring, such as Webforta Monitor, can help you notice unexpected outages or DNS changes after a network device incident, though it cannot confirm whether this flaw was used. For broader habits that reduce risk from network gear, see our guide to small business website security.
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.
