Multiple DrayTek VigorSwitch models contain unauthorized operation vulnerabilities in multiple syslog functions. The vulnerability is caused by missing authorization checks. A remote attacker can trigger these vulnerabilities via crafted requests to modify configuration, restart services, save startup configuration, or clear logs.
CVE-2026-71933
Score 9.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. a secondary CVSS source baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 56(Track)EG Risk 56/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 26, 2026
Advisory Details (2)
Auto-updated Aug 29, 2026DrayTek VigorSwitch Multiple Models Missing Authorization in Syslog Functions | Advisories | VulnCheck
https://www.vulncheck.com/advisories/draytek-vigorswitch-multiple-models-missing-authorization-in-syslog-functionsMultiple Vulnerabilities in VigorSwitch Series | DrayTek
https://www.draytek.com/about/security-advisory/multiple-vulnerabilities-in-vigorswitch-series-august-2026/Vendor Advisories for CVE-2026-71933(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 47× in last 7d / 47× 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 05:39 UTCGHSA enrichment
- 2026-08-30 01:37 UTCEG score recompute
- 2026-08-30 01:37 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:35 UTCGHSA enrichment
- 2026-08-29 17:33 UTCGHSA enrichment
- 2026-08-29 12:38 UTCGHSA enrichment
- 2026-08-29 08:33 UTCGHSA enrichment
- 2026-08-29 04:32 UTCGHSA enrichment
- 2026-08-29 00:22 UTCEG score recompute
- 2026-08-29 00:22 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 18:49 UTCGHSA enrichment
- 2026-08-28 14:30 UTCGHSA enrichment
- 2026-08-28 10:27 UTCGHSA enrichment
- 2026-08-28 06:21 UTCGHSA enrichment
- 2026-08-28 02:20 UTCGHSA enrichment
- 2026-08-27 22:16 UTCGHSA enrichment
- 2026-08-27 18:14 UTCEG score recompute
- 2026-08-27 18:14 UTCGHSA enrichment
- 2026-08-27 13:37 UTCGHSA enrichment
- 2026-08-27 09:36 UTCGHSA enrichment
- 2026-08-27 05:33 UTCGHSA enrichment
- 2026-08-27 01:27 UTCGHSA enrichment
- 2026-08-26 21:25 UTCGHSA enrichment
Show 22 moreShow fewer
- 2026-08-26 17:23 UTCEG score recompute
- 2026-08-26 17:23 UTCGHSA enrichment
- 2026-08-26 16:23 UTCEG score recompute
- 2026-08-26 16:23 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 14:45 UTCGHSA enrichment
- 2026-08-26 10:43 UTCGHSA enrichment
- 2026-08-26 06:42 UTCGHSA enrichment
- 2026-08-26 02:40 UTCGHSA enrichment
- 2026-08-25 22:38 UTCGHSA enrichment
- 2026-08-25 18:36 UTCGHSA enrichment
- 2026-08-25 14:34 UTCEG score recompute
- 2026-08-25 14:34 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 10:32 UTCGHSA enrichment
- 2026-08-25 06:30 UTCGHSA enrichment
- 2026-08-25 02:24 UTCGHSA enrichment
- 2026-08-24 22:23 UTCEG score recompute
- 2026-08-24 22:23 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)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p90CRITICAL
- CVE-2018-1217EG 9.8EPSS p97CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-71933?
When was CVE-2026-71933 disclosed?
Is CVE-2026-71933 actively exploited?
What is the CVSS score of CVE-2026-71933?
How do I remediate CVE-2026-71933?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71933
Is Your Infrastructure Affected by CVE-2026-71933?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.