Vulnerability in Ruckus Networks Vriot Iot Controller
CVE-2025-69426
The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating system user account within an initialization script. The SSH service is network-accessible without IP-based restrictions. Although the configuration disables SCP and pseudo-TTY allocation, an attacker can authenticate using the hardcoded credentials and establish SSH local port forwarding to access the Docker socket. By mounting the host filesystem via Docker, an attacker can escape the container and execute arbitrary OS commands as root on the underlying vRIoT controller, resulting in complete system compromise.
Published · last modified .
EPSS exploit prediction
EPSS: 0.004 (31.7th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 31.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: +0.000
Affected products
- Ruckus Networks Vriot Iot Controller — versions 2.3.0.0 (GA), 2.3.1.0 (MR), 2.4.0.0 (GA)
Weakness classification (CWE)
References
- support.ruckuswireless.com/security_bulletins/336 (vendor-advisory, patch)
- www.vulncheck.com/advisories/ruckus-vriot-iot-controller-hardcoded-ssh-credenti… (third-party-advisory)