CVE
DrayTek Vigor2960 stack buffer overflow in mainfunction.cgi
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
Summary
DrayTek Vigor2960 is affected by a stack-based buffer overflow in the setSWMProfile function of /cgi-bin/mainfunction.cgi. An attacker on the network, who needs low-privilege login, can trigger it remotely by manipulating the filename argument.
Original description
A weakness has been identified in DrayTek Vigor2960 up to 1.5.1.6. Affected is the function setSWMProfile of the file /cgi-bin/mainfunction.cgi. Executing a manipulation of the argument filename can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. Upgrading to version 1.5.1.7 is able to address this issue. It is recommended 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."
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132139 (DrayTek Vigor2960 mainfunction.cgi setSWMProfile stack-based overflow), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132139 (entry last updated 2026-11-18):
Affected:
- DrayTek Vigor2960: versions 1.5.1.0, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4, 1.5.1.5, 1.5.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132139 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132139 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
- https://vuldb.com/vuln/439439
- https://vuldb.com/vuln/439439/cti
- https://vuldb.com/cve/CVE-2026-132139
- https://vuldb.com/submit/1044966
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132139
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132139"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- DrayTek Vigor2960
1.5.1.0, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4, 1.5.1.5, 1.5.1.6
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Patch | fw.draytek.com.tw · Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132139 |
| Record | NVD · CVE-2026-132139 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · yikesoftware/DrayTek_Vigor2960_Security_Analysis · tree/main/cases/DRV2960-0021-authenticated-setswmprofile-filename-stack-overflow |
| Other links 4 | |
| Advisory | VulDB · Advisory #439439 |
| Advisory | VulDB · Threat intelligence #439439 |
| Advisory | VulDB · CVE-2026-132139 record |
| Advisory | VulDB · Submission #1044966 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132139
Is CVE-2026-132139 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132139?
Vigor2960: versions 1.5.1.0, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4 and 2 more.Source: cve.now feed data