On November 15, 2026, VulDB (acting as CNA) filed five CVEs in NVD against the DrayTek Vigor2960 VPN router running firmware 1.5.1.6. Four score 9.9 and one 9.1 in CVSS 3.1. They all hit the same binary, /cgi-bin/mainfunction.cgi, the CGI behind the web management interface, and for every one of them an exploit has been made public.
The Vigor2960 isn't a consumer router. It's a VPN concentrator and load balancer that sits at the edge of small business networks and branch sites. Compromising it means controlling what enters and leaves the network.
| CVE | Function / parameter | Flaw | CVSS 3.1 (VulDB) | Privileges required |
|---|---|---|---|---|
| CVE-2026-129449 | sub_14914, swmconfigupload | Command injection (CWE-77) | 9.9 | Low (PR:L) |
| CVE-2026-129450 | sub_1E084, action=doWebBackup, option | Path traversal (CWE-22) | 9.9 | Low (PR:L) |
| CVE-2026-129451 | app_guest_export, filename | Path traversal (CWE-22) | 9.9 | Low (PR:L) |
| CVE-2026-129452 | set_table, jsondata | Command injection (CWE-77) | 9.1 | High (PR:H) |
| CVE-2026-129453 | check_file_exist, upload_name | Heap-based overflow (CWE-122) | 9.9 | Low (PR:L) |
The four 9.9 ratings share the vector AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; CVE-2026-129452 carries PR:H, hence its 9.1. VulDB also publishes CVSS 4.0 scores (8.6, and 8.5 for CVE-2026-129452) and CVSS 2.0 scores. All five are Deferred in NVD: NIST won't analyze them or attach CPE configurations. None is in the CISA KEV catalog at the time of writing.
What the five flaws do
All of them require an authenticated session on the web interface, so none is pre-auth. But PR:L means a low-privileged account is enough for four of them, and S:C (changed scope) means the impact reaches beyond the vulnerable component: you go from the web UI to the router's operating system.
Two command injections
- CVE-2026-129449: the
swmconfiguploadparameter handled bysub_14914ends up in a system command. - CVE-2026-129452: same outcome through the
jsondataargument ofset_table. This one needs a highly privileged account.
Command injection on a router is code execution on the device: rule changes, traffic interception, persistence.
Two path traversals
- CVE-2026-129450: the
optionargument of thedoWebBackupaction. - CVE-2026-129451: the
filenameargument ofapp_guest_export.
The names of the research write-ups cited as references mention file overwrite ("clobber") and write/delete. That's worse than a read-only traversal: writing arbitrary files on an embedded system often leads to code execution. This is our inference; the NVD description stops at path traversal.
One heap overflow
- CVE-2026-129453: the
upload_nameargument ofcheck_file_exist(the file existence check) triggers a heap-based buffer overflow.
Affected versions and fix
The descriptions target firmware 1.5.1.6 ("up to 1.5.1.6" for CVE-2026-129449 and 129451) and state that upgrading to 1.5.1.7 resolves the issue. A download link for firmware 1.5.1.7 on DrayTek's server is among the NVD references.
The vendor statement quoted in each description deserves a close read. DrayTek points out that 1.5.1.6 isn't the latest 2960 release, that the latest one fixes many security issues, and that another release is planned to address the reported flaws. In other words, 1.5.1.7 is the floor, not necessarily the end of the story: keep an eye on the Vigor2960 firmware page for the next build.
With no CPE data, these CVEs won't show up in a product search that relies only on NIST analysis.
Detection
- Firmware version: any Vigor2960 still on 1.5.1.6 or earlier is affected.
- Exposure: is the management interface (HTTP/HTTPS) reachable from the WAN? That's the deciding question, since every one of these flaws goes through the web UI.
- Accounts: list the web interface accounts. With
PR:L, every secondary account, even read-only, is a possible way in. - Logs: requests to
mainfunction.cgiwith../sequences or shell metacharacters (;,|,`,$() in theswmconfigupload,jsondata,option,filenameorupload_nameparameters. - Configuration: diff the running config against your last known-good backup (NAT rules, VPN tunnels, accounts).
Mitigation
1. Move to 1.5.1.7, then track the next release
That's the fix NVD cites. Plan for the follow-up release DrayTek has announced as well.
2. Close management on the WAN side
The management interface of a VPN concentrator should only be reachable from an admin network, or through the VPN itself.
3. Trim and rotate accounts
Remove unneeded web accounts and change the remaining passwords. A PR:L flaw turns a weak or reused password into code execution.
4. If you suspect compromise
Don't just update: an attacker who ran code may have changed the configuration. Restore from a clean config and rotate the secrets stored on the device (VPN keys and pre-shared secrets).
Routers keep showing up in these waves of CVEs with public exploits, as October's TOTOLINK, Tenda and D-Link flaws showed. The difference this time is that the target is a business-grade device sitting inline on the network.
Why continuous monitoring matters for network gear
A VPN router gets updated rarely, often by a single person, and its CVEs arrive without CPE data when NIST marks them "Deferred." That's exactly when a manual product search comes back empty.
With cveo.tech, add your Vigor2960 units and their firmware version to your inventory and get an alert as soon as a CVE that affects them is published, even when NVD doesn't analyze it.