Skip to main content
VulnerabilityPublished

CVE-2026-132139: DrayTek Vigor2960 · Memory Buffer Overflow

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-132139· Critical 9.4

Public exploit available · CVSS 9.4 Critical.

Data as of 18 Nov 2026, 22:48 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.09.4
CNA (VulDB)CVSS 3.19.9
CNA (VulDB)CVSS 3.09.9
CNA (VulDB)CVSS 2.09.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
DrayTekVigor2960Affected
  • 1.5.1.0 – 1.5.1.6
7 affected builds
Fixed in–

AI-suggested

Upgrade DrayTek Vigor2960 devices to firmware version 1.5.1.7 or later, as this version addresses the buffer overflow vulnerability. The vendor confirms that 1.5.1.6 is not the latest version and that the latest release fixes multiple security issues including this one. No other mitigations are indicated.

Description

A critical stack-based buffer overflow vulnerability exists in the setSWMProfile function of DrayTek Vigor2960 firmware versions up to 1.5.1.6. This flaw can be exploited remotely by manipulating the filename argument, potentially allowing an attacker to execute arbitrary code with high impact on confidentiality, integrity, and availability. Public exploit code is available. Upgrading to version 1.5.1.7 addresses this issue.

References

Community reviews

Loading reviews…