Skip to content
Fencer Intel
critical 9.8

CVE-2020-26879 in the critical feed json

Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py.

published 6y ago modified 4mo ago also EUVD-2020-19414

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
44.4%
EPSS 44.4% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Is CVE-2020-26879 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

44.37% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Ruckus vRioT IoT Controller - Authentication Bypass nuclei detection template
  • adepts.of0x.cc https://adepts.of0x.cc/ruckus-vriot-rce/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.