CVE-2025-44954: RUCKUS SmartZone · Use of Default Cryptographic Key
Affects RUCKUS SmartZoneSource CVE Database V5
Not known to be exploited · CVSS 9.0 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RUCKUS SmartZone | Affected
| Fixed in– |
AI-suggested
1. Immediate upgrade: Organizations should prioritize upgrading RUCKUS SmartZone to version 6.1.2p3 Refresh Build or later, where this vulnerability is addressed. 2. Network segmentation: Isolate SmartZone management interfaces from general network access, restricting SSH access to trusted administrative hosts only. 3. SSH key management: Audit all SSH keys on SmartZone devices and replace any default or hardcoded keys with unique, securely generated keys. 4. Access controls: Implement strict access control policies and multi-factor authentication for network management systems to reduce risk of unauthorized access. 5. Monitoring and detection: Deploy network monitoring and intrusion detection systems to identify anomalous SSH login attempts or unusual administrative activity on SmartZone devices. 6. Incident response readiness: Prepare incident response plans specific to network infrastructure compromise, including forensic analysis of SmartZone devices. 7. Vendor communication: Maintain close communication with RUCKUS for timely updates, patches, and advisories related to this vulnerability. 8. Temporary mitigations: If immediate patching is not feasible, disable SSH access to SmartZone devices or restrict it via firewall rules until the patch can be applied.
Description
RUCKUS SmartZone (SZ) before 6.1.2p3 Refresh Build has a hardcoded SSH private key for a root-equivalent user account.