Critical root-access risk on widely deployed IoT controller; exploit could disrupt networks across multiple environments.
CVE-2025-69425
Root command execution via hardcoded TOTP/token in Ruckus vRIoT firmware (<3.0.0.0).
Is CVE-2025-69425 being exploited?
Not confirmed. CVE-2025-69425 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.87% probability of exploitation in the next 30 days.
How severe is CVE-2025-69425?
CVE-2025-69425 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-69425?
Yes. A fix has been recorded for CVE-2025-69425. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-69425 affect?
CVE-2025-69425 affects Ruckus vRIoT IoT Controller firmware < 3.0.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-69425?
Upgrade to 3.0.0.0+ firmware; rotate credentials; disable exposed port if feasible.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can obtain root access and execute OS commands via port 2004, fully compromising the device.
Immediate action required
- affected>= 2.3.0.0 (GA) and < 3.0.0.0 (GA)
- affected>= 2.3.1.0 (MR) and < 3.0.0.0 (GA)
- affected>= 2.4.0.0 (GA) and < 3.0.0.0 (GA)
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.