CVE-2020-26879

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 45.1%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 45%CVSS: 9.8Exploit: NoneExposed: 0

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

Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
67(Track*)
EG Risk 67/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
Severity98% × 45%
Exploitation45% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.7%
KEV
Not listed

Published

October 26, 2020

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jun 11, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

20201026 | Security Bulletins | Ruckus Wireless Support

https://support.ruckuswireless.com/security_bulletins/305
generic

Technical Documents | Ruckus Wireless Support

https://support.ruckuswireless.com/documents
generic🟡 PoC Available

Remote Command Execution in Ruckus IoT Controller (CVE-2020-26878 & CVE-2020-26879) - Adepts of 0xCC

https://adepts.of0x.cc/ruckus-vriot-rce/
generic

Adepts of 0xCC

https://adepts.of0x.cc
generic🟡 PoC Available

Doomsday Vault | X-C3LL’s Personal Blog :)

https://x-c3ll.github.io
generic

X-C3LL (@TheXC3LL) / X

https://twitter.com/TheXC3LL

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 37× 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-07-23 01:52 UTCEG score recompute
  2. 2026-07-22 22:38 UTCEG score recompute
  3. 2026-07-22 14:05 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 16:55 UTCEPSS rescore
  15. 2026-07-15 01:57 UTCEPSS rescore
  16. 2026-07-13 22:27 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 06:10 UTCEPSS rescore
  19. 2026-07-13 06:10 UTCEPSS rescore
  20. 2026-07-12 05:44 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-09 19:07 UTCEPSS rescore
  24. 2026-07-08 15:12 UTCEPSS rescore
  25. 2026-07-06 02:21 UTCEPSS rescore
Show 39 more
  1. 2026-07-06 02:21 UTCEPSS rescore
  2. 2026-07-04 06:29 UTCEPSS rescore
  3. 2026-07-04 06:29 UTCEPSS rescore
  4. 2026-06-28 04:54 UTCEPSS rescore
  5. 2026-06-28 04:54 UTCEPSS rescore
  6. 2026-06-27 03:06 UTCEPSS rescore
  7. 2026-06-27 03:06 UTCEPSS rescore
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-24 14:03 UTCEPSS rescore
  10. 2026-06-24 14:03 UTCEPSS rescore
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-21 14:54 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-19 19:24 UTCEPSS rescore
  17. 2026-06-19 19:23 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-18 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-15 17:46 UTCEPSS rescore
  23. 2026-06-12 23:10 UTCEPSS rescore
  24. 2026-06-11 13:58 UTCEPSS rescore
  25. 2026-06-10 22:16 UTCEPSS rescore
  26. 2026-06-10 13:20 UTCEPSS rescore
  27. 2026-06-07 15:23 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-07 15:23 UTCEPSS rescore
  30. 2026-06-05 22:45 UTCEPSS rescore
  31. 2026-06-05 22:45 UTCEPSS rescore
  32. 2026-06-01 13:50 UTCEPSS rescore
  33. 2026-05-29 13:42 UTCEPSS rescore
  34. 2026-05-28 13:43 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-27 13:39 UTCEPSS rescore
  37. 2026-05-27 13:39 UTCEPSS rescore
  38. 2026-05-23 06:04 UTCEG score recompute
  39. 2026-05-23 06:04 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2020/CVE-2020-26879.yaml
    First seen Jan 1, 2020

    Ruckus vRioT IoT Controller - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-26879?
CVE-2020-26879 is a critical vulnerability published on October 26, 2020. Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.
When was CVE-2020-26879 disclosed?
CVE-2020-26879 was first published in the National Vulnerability Database on October 26, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26879 actively exploited?
CVE-2020-26879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-26879?
CVE-2020-26879 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-26879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-26879, 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-2020-26879

Explore →

Is Your Infrastructure Affected by CVE-2020-26879?

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

Start Free Scan →Browse All CVEs