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.
CVE-2026-71920
Score 4.9 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 4.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 4.9(high)
- EG Risk
- 22(Track)EG Risk 22/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity49% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 24, 2026DrayTek VigorSwitch Multiple Models NULL Pointer Dereference via formlogout | Advisories | VulnCheck
https://www.vulncheck.com/advisories/draytek-vigorswitch-multiple-models-null-pointer-dereference-via-formlogoutMultiple Vulnerabilities in VigorSwitch Series | DrayTek
https://www.draytek.com/about/security-advisory/multiple-vulnerabilities-in-vigorswitch-series-august-2026/Vendor Advisories for CVE-2026-71920(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 02:19 UTCEG score recompute
- 2026-08-30 02:19 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 00:26 UTCEG score recompute
- 2026-08-29 00:25 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 19:17 UTCEG score recompute
- 2026-08-27 19:17 UTCGHSA enrichment
- 2026-08-26 17:24 UTCEG score recompute
- 2026-08-26 17:24 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 21:40 UTCEG score recompute
- 2026-08-25 21:40 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 19:25 UTCEG score recompute
- 2026-08-24 19:25 UTCGHSA enrichment
- 2026-08-24 18:22 UTCEG score recompute
- 2026-08-24 17:21 UTCEG score recompute
- 2026-08-24 17:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-71920?
When was CVE-2026-71920 disclosed?
Is CVE-2026-71920 actively exploited?
What is the CVSS score of CVE-2026-71920?
How do I remediate CVE-2026-71920?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71920
Is Your Infrastructure Affected by CVE-2026-71920?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.