Skip to main content
CVE-2025-44957VulnerabilityPublished Updated

CVE-2025-44957: RUCKUS SmartZone · Authentication Bypass Using an Alternate Path or Channel

Affects RUCKUS SmartZoneSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2025

  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

Affected software

ProductAffectedFixed in
RUCKUS SmartZoneAffected
  • =0
Fixed in–

AI-suggested

European organizations should immediately inventory their Ruckus SmartZone deployments and verify the software version in use. Upgrading to version 6.1.2p3 Refresh Build or later, once available, is the primary mitigation step. Until patches are applied, restrict network access to the SmartZone management interfaces by implementing strict network segmentation and firewall rules limiting API access to trusted hosts only. Review and rotate API keys regularly, enforcing the principle of least privilege to minimize the impact of compromised keys. Implement monitoring and logging of API usage to detect anomalous or unauthorized access attempts. Employ multi-factor authentication (MFA) where possible for administrative access to reduce the risk of credential misuse. Coordinate with Ruckus support for any available interim mitigations or workarounds. Additionally, conduct security awareness training for administrators managing network infrastructure to recognize and respond to suspicious activities promptly.

Description

Ruckus SmartZone (SZ) before 6.1.2p3 Refresh Build allows authentication bypass via a valid API key and crafted HTTP headers.

References

Community reviews

Loading reviews…