Vulnerability record

CVE-2020-26879

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

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. Source description excerpt; complete tracked detail loads below.

NVD published: Oct 27, 2020 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

commscope — ruckus_vriot. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Oct 27, 2020 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Act · 458.7

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Reported

kev-listed · VulnCheck KEV

VulnCheck KEV added: Jun 28, 2022 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Evidence detail

Loading the full tracker evidence record…