CVE-2026-71929

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. A secondary CVSS source baseline 7.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 7.2Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists DrayTek Corporation VigorSwitch G2540xs versions before 3.9.10; DrayTek Corporation VigorSwitch P2540xs versions before 3.9.10; DrayTek Corporation VigorSwitch FX2120 versions before 3.9.10 as affected, and 5 more products. No release containing a fix is confirmed on record.

Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevProto function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
33
EG Risk 33/100

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 computed (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation2.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
2.3%
EPSS %ILE
82nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
No fix on record yet.
Web page

DrayTek VigorSwitch Multiple Models OS Command Injection via setDevProto | Advisories | VulnCheck

https://www.vulncheck.com/advisories/draytek-vigorswitch-multiple-models-os-command-injection-via-setdevproto
Web page

Multiple Vulnerabilities in VigorSwitch Series | DrayTek

https://www.draytek.com/about/security-advisory/multiple-vulnerabilities-in-vigorswitch-series-august-2026/

Vendor Advisories for CVE-2026-71929(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 / 98× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 177 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-10-12 22:26 UTCEG score recompute
  3. 2026-10-12 22:26 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-10-12 15:42 UTCEG score recompute
  6. 2026-10-11 19:28 UTCEG score recompute
  7. 2026-10-11 16:43 UTCEG score recompute
  8. 2026-10-11 14:03 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  11. 2026-10-10 12:34 UTCEG score recompute
  12. 2026-10-10 12:34 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  14. 2026-10-09 04:50 UTCEG score recompute
  15. 2026-10-09 04:50 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  17. 2026-10-08 03:53 UTCEG score recompute
  18. 2026-10-08 03:52 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-10-07 04:28 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  21. 2026-10-06 16:11 UTCEG score recompute
  22. 2026-10-06 16:11 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  24. 2026-10-06 02:49 UTCEG score recompute
  25. 2026-10-06 02:49 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-10-05 09:21 UTCEG score recompute
  3. 2026-10-05 09:21 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-10-04 20:42 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  6. 2026-10-04 04:54 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  7. 2026-10-03 16:31 UTCEG score recompute
  8. 2026-10-03 16:31 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-10-02 21:37 UTCEG score recompute
  11. 2026-10-02 21:37 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  12. 2026-10-02 09:19 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  13. 2026-10-01 21:02 UTCEG score recompute
  14. 2026-10-01 21:02 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-10-01 08:35 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  17. 2026-09-30 20:18 UTCEG score recompute
  18. 2026-09-30 20:18 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-09-30 07:02 UTCEG score recompute
  21. 2026-09-30 07:02 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  22. 2026-09-29 15:11 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  23. 2026-09-29 01:40 UTCEG score recompute
  24. 2026-09-29 01:40 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  26. 2026-09-28 12:57 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  27. 2026-09-28 00:40 UTCEG score recompute
  28. 2026-09-28 00:40 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  29. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  30. 2026-09-27 12:21 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  31. 2026-09-27 00:04 UTCEG score recompute
  32. 2026-09-27 00:04 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  34. 2026-09-25 16:03 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  35. 2026-09-25 01:51 UTCEG score recompute
  36. 2026-09-25 01:51 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  37. 2026-09-24 13:33 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  38. 2026-09-24 01:15 UTCEG score recompute
  39. 2026-09-24 01:15 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  41. 2026-09-23 12:58 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  42. 2026-09-23 00:41 UTCEG score recompute
  43. 2026-09-23 00:41 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  44. 2026-09-22 12:24 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  45. 2026-09-22 00:06 UTCEG score recompute
  46. 2026-09-22 00:06 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  47. 2026-09-21 21:09 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  48. 2026-09-21 11:48 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  49. 2026-09-20 23:26 UTCEG score recompute
  50. 2026-09-20 23:26 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  51. 2026-09-20 20:16 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  52. 2026-09-20 10:48 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  53. 2026-09-19 22:31 UTCEG score recompute
  54. 2026-09-19 22:31 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  55. 2026-09-19 10:07 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  56. 2026-09-18 21:48 UTCEG score recompute
  57. 2026-09-18 21:48 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  58. 2026-09-18 19:28 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  59. 2026-09-18 09:31 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  60. 2026-09-17 21:12 UTCEG score recompute
  61. 2026-09-17 21:12 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  62. 2026-09-17 07:49 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  63. 2026-09-16 19:31 UTCEG score recompute
  64. 2026-09-16 19:30 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  65. 2026-09-16 14:08 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  66. 2026-09-16 07:03 UTCEG score recompute
  67. 2026-09-16 07:03 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  68. 2026-09-16 05:15 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  69. 2026-09-15 18:45 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  70. 2026-09-15 05:43 UTCEG score recompute
  71. 2026-09-15 05:43 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  72. 2026-09-15 03:12 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  73. 2026-09-14 16:54 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2
  74. 2026-09-14 04:37 UTCEG score recompute
  75. 2026-09-14 04:37 UTCGHSA enrichmentGHSA-p299-wp3x-668q · GitHub severity HIGH · GitHub CVSS 7.2

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71929?
CVE-2026-71929 is a high-severity vulnerability; its CVE record was published on August 24, 2026. Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevProto function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to…
When was CVE-2026-71929 made public?
CVE-2026-71929 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-71929 actively exploited?
CVE-2026-71929 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71929?
CVE-2026-71929 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71929?
No fix for CVE-2026-71929 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists DrayTek Corporation VigorSwitch G2540xs versions before 3.9.10; DrayTek Corporation VigorSwitch P2540xs versions before 3.9.10; DrayTek Corporation VigorSwitch FX2120 versions before 3.9.10 as affected, and 5 more products. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-71929 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71929

Explore →

Is Your Infrastructure Affected by CVE-2026-71929?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs