CVE-2026-71931
Auth-required command injection in DrayTek VigorSwitch tftp_upgrade
Is CVE-2026-71931 being exploited?
Not confirmed. CVE-2026-71931 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.4% probability of exploitation in the next 30 days.
How severe is CVE-2026-71931?
CVE-2026-71931 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71931?
Not known from our data. No patch reference has been recorded for CVE-2026-71931, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71931 affect?
CVE-2026-71931 affects DrayTek VigorSwitch (multiple models), Web management interface (admin access), tftp_upgrade feature. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71931?
Apply vendor patch when released; restrict admin access, disable TFTP upgrade, segment management VLANs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker with valid admin credentials can execute arbitrary commands as root via crafted TFTP filename.
Patch when possible
- affected< 3.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.10.6
- affected< 2.9.10
- affected< 3.9.10
- affected< 3.10.6
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.10.6
- affected< 2.9.10
- affected< 3.9.10
- affected< 3.10.6
- affected< 3.10.6
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.10.7
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.9.10
- affected< 2.10.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.