# CVE-2026-129449: DrayTek Vigor2960 mainfunction.cgi sub_14914 command injection

> Remote attackers can inject commands via the swmconfigupload argument on DrayTek Vigor2960 routers.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-6vqp-3x8r-9qrr

## What is CVE-2026-129449?

CVE-2026-129449 is a critical command injection vulnerability in DrayTek Vigor2960, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in DrayTek Vigor2960 up to 1.5.1.6. Affected by this vulnerability is the function sub_14914 of the file /cgi-bin/mainfunction.cgi. The manipulation of the argument swmconfigupload leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.5.1.7 addresses this issue. It is advisable to upgrade the affected component. The vendor recommends: "1.5.1.6 isn't the latest version of 2960, the latest version fixes many security issues. And we have another one in our release plan which should solve the issues reported."

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-129449?

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.


Products: DrayTek Vigor2960.

CPE match criteria (CPE 2.3):

- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.0 up to 1.5.1.0
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.1 up to 1.5.1.1
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.2 up to 1.5.1.2
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.3 up to 1.5.1.3
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.4 up to 1.5.1.4
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.5 up to 1.5.1.5
- `cpe:2.3:o:draytek:vigor2960_firmware:*:*:*:*:*:*:*:*` from 1.5.1.6 up to 1.5.1.6

## How do I fix CVE-2026-129449?

No fix has been published for CVE-2026-129449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129449 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129449 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129449 and fix it if it is affected.

What it is: CVE-2026-129449 is a critical command injection vulnerability in DrayTek Vigor2960, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129449 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: DrayTek Vigor2960. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129449/ (Markdown: https://insights.sbomify.com/CVE-2026-129449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129449
- OSV: https://osv.dev/vulnerability/CVE-2026-129449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129449/
Summaries are generated and may contain mistakes; the official description above is the record.
