Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71922 – Pre-Auth Denial of Service (Null Pointer Dereference) – DrayTek VigorSwitch Series

Be the first to know when new zero-days emerge:

Summary

CVE-2026-71922 is a pre-authentication NULL pointer dereference vulnerability (CWE-476) affecting the setget.cgi interface on multiple DrayTek VigorSwitch models. The flaw is triggered when a required pass field is missing from a request, causing the switch’s management service to crash. The vulnerability carries a CVSS v4.0 base score of 8.7 (High) and can be exploited remotely over the network with no authentication or user interaction, resulting in a denial-of-service condition.

Technical details

  • Root cause: The setget.cgi CGI handler on affected VigorSwitch firmware fails to validate the presence of the pass field before dereferencing it, leading to a NULL pointer dereference.
  • Trigger conditions: An attacker sends a specially crafted HTTP request to the setget.cgi endpoint that omits the expected pass parameter.
  • Attack vector: Network-based, pre-authentication — no credentials, privileges, or user interaction are required (AV:N/AC:L/PR:N/UI:N).
  • Impact: Causes the affected switch management service to crash, resulting in denial of service (availability impact only; no confidentiality or integrity impact per the CVSS vector). Repeated exploitation could be used to persistently disrupt switch management/administration availability.
  • Credit: Discovered by Jincheng Wang and Le Yu (Nanjing University) and Xiapu Luo (Hong Kong Polytechnic University).

Affected software

Multiple DrayTek VigorSwitch models, prior to the following fixed firmware versions:

  • VigorSwitch G2540xs, P2540xs, FX2120 — versions prior to 3.9.10
  • VigorSwitch G2282x, P2282x — versions prior to 2.10.6
  • VigorSwitch Q2300x, PQ2300xb — versions prior to 2.10.7
  • VigorSwitch G2542x, P2542x, P2542xh — versions prior to 3.10.6
  • VigorSwitch PX2060, G1280, P1280, P1281x, G1282, P1282 — versions prior to 2.9.10
  • VigorSwitch G2121, P2121, PQ2121x, Q2121x, G2280x, P2280x, Q2200x, PQ2200xb, G2100, P2100, G2540x, P2540x — versions prior to 2.9.10

Severity

  • CVSS v4.0: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • Immediate: Upgrade affected VigorSwitch models to the fixed firmware versions listed above (3.9.10, 2.10.6, 2.10.7, 3.10.6, or 2.9.10, depending on model), as published in DrayTek’s security advisory.
  • If patching cannot be performed immediately:
    • Restrict access to the switch management interface (including setget.cgi) to trusted internal networks only; do not expose switch management interfaces directly to the internet.
    • Use firewall/ACL rules or a management VLAN to limit which hosts can reach the switch’s web management CGI endpoints.
    • Monitor for repeated crashes or unavailability of the switch management service, which may indicate exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge