Skip to main content
CVE-2025-69425VulnerabilityPublished Updated

CVE-2025-69425: RUCKUS Networks vRIoT IoT Controller · Missing Authentication

Affects RUCKUS Networks vRIoT IoT ControllerSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 3.0.0.0 (GA) as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.0.0 (GA)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade RUCKUS Networks vRIoT IoT Controller to 3.0.0.0 (GA).

Affected software

ProductAffectedFixed in
RUCKUS NetworksvRIoT IoT ControllerAffected
  • ≥ 2.3.0.0 (GA), < 3.0.0.0 (GA)
  • ≥ 2.3.1.0 (MR), < 3.0.0.0 (GA)
  • ≥ 2.4.0.0 (GA), < 3.0.0.0 (GA)
Fixed in
  • 3.0.0.0 (GA)

AI-suggested

If you cannot patch yet, restrict network access to TCP port 2004 on affected devices to trusted administrators only and monitor for unauthorized access attempts. Consider isolating affected devices from untrusted networks to reduce exposure.

Description

The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) expose a command execution service on TCP port 2004 running with root privileges. Authentication to this service relies on a hardcoded Time-based One-Time Password (TOTP) secret and an embedded static token. An attacker who extracts these credentials from the appliance or a compromised device can generate valid authentication tokens and execute arbitrary OS commands with root privileges, resulting in complete system compromise.

References

Community reviews

Loading reviews…