CVE-2026-71915

HIGHPre-NVD 7.27.2
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this week
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 7.2Exploit: None knownExposed: 0

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

Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the jsonstatus function. The vulnerability is caused by insufficient filtering of the usescript, usefile, and option 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.2(high)
EG Risk
34(Track)
EG Risk 34/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 computed
Severity72% × 45%
Exploitation3% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
87%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Aug 24, 2026
No patch confirmed yet.
generic

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

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

Vendor Advisories for CVE-2026-71915(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 26× in last 7d / 26× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCGHSA enrichment
  3. 2026-08-29 13:58 UTCGHSA enrichment
  4. 2026-08-29 02:31 UTCEG score recompute
  5. 2026-08-29 02:31 UTCGHSA enrichment
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 15:06 UTCGHSA enrichment
  8. 2026-08-28 03:42 UTCGHSA enrichment
  9. 2026-08-27 16:18 UTCEG score recompute
  10. 2026-08-27 16:18 UTCGHSA enrichment
  11. 2026-08-27 04:51 UTCGHSA enrichment
  12. 2026-08-26 17:24 UTCEG score recompute
  13. 2026-08-26 17:24 UTCGHSA enrichment
  14. 2026-08-26 14:47 UTCEPSS rescore
  15. 2026-08-26 05:37 UTCGHSA enrichment
  16. 2026-08-25 18:13 UTCEG score recompute
  17. 2026-08-25 18:13 UTCGHSA enrichment
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 06:49 UTCGHSA enrichment
  20. 2026-08-24 19:25 UTCEG score recompute
  21. 2026-08-24 19:25 UTCGHSA enrichment
  22. 2026-08-24 19:07 UTCEG score recompute
  23. 2026-08-24 19:07 UTCGHSA enrichment
  24. 2026-08-24 18:22 UTCEG score recompute
  25. 2026-08-24 17:21 UTCEG score recompute
Show 1 more
  1. 2026-08-24 17:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71915?
CVE-2026-71915 is a high vulnerability published on August 24, 2026. Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the jsonstatus function. The vulnerability is caused by insufficient filtering of the usescript, usefile, and option fields before command execution. A remote attacker can trigger this vulnerability via crafted input…
When was CVE-2026-71915 disclosed?
CVE-2026-71915 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71915 actively exploited?
CVE-2026-71915 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 13.4% of all scored CVEs.
What is the CVSS score of CVE-2026-71915?
CVE-2026-71915 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-71915?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71915, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-71915?

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