CVE-2020-26879

Exp

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.

Published: 2020-10-26 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-26879 is rated High Exploit Risk (89.6/100): CVSS Critical severity, with high exploitation likelihood (EPSS 88.90%, 100th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-26879

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-26879

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-05 88.29% 88.90% +0.61%
2 2026-04-16 89.45% 88.29% -1.17%
3 2026-01-12 — 89.45% —

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-26879

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
10.0 2.0 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 10.0 [email protected]

Weakness enumeration for CVE-2020-26879

Affected software / configurations for CVE-2020-26879

Vendor Product Version Raw CPE
commscope ruckus_vriot <= 1.5.1.0.21 cpe:2.3:a:commscope:ruckus_vriot:*:*:*:*:*:*:*:*

References for CVE-2020-26879

URL Tags
https://adepts.of0x.cc Third Party Advisory
https://adepts.of0x.cc/ruckus-vriot-rce/ Exploit Third Party Advisory
https://support.ruckuswireless.com/documents Vendor Advisory
https://support.ruckuswireless.com/security_bulletins/305 Product Vendor Advisory
https://twitter.com/TheXC3LL Third Party Advisory
https://x-c3ll.github.io Third Party Advisory
cvelogic Threat Intelligence