CVE-2026-71920

DrayTek VigorSwitch Multiple Models NULL Pointer Dereference via formlogout

MEDIUM
4.9
CVSS Score
Published: August 24, 2026 at 05:07 PM UTC
Updated: October 13, 2026 at 09:10 AM UTC
42 products affected across 1 vendorVigorswitch Q2200X FirmwareVigorswitch PQ2121X FirmwareVigorswitch PQ2200XB Firmware

Using VigorSwitch G2540xs by DrayTek Corporation?

Get instant alerts when new vulnerabilities affect VigorSwitch G2540xs - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.9
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

Multiple DrayTek VigorSwitch models contain a null pointer dereference vulnerability in the formlogout function. The vulnerability is caused by missing checks for an empty or absent Cookie header before string handling. A remote attacker can trigger this vulnerability via a crafted request to crash the service and cause a denial of service. Exploitation requires valid administrative credentials for the device's web management interface.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.9.10
Affected range stops below 3.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 3.9.10
Affected range stops below 3.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 2.9.10
Affected range stops below 2.9.10, so it looks safe — our inference, not a vendor statement
v < 3.9.10
Affected range stops below 3.9.10, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.9MEDIUMVulnCheck
Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card