Skip to main content
VulnerabilityPublished Updated

CVE-2025-46117: CommScope Ruckus Unleashed · OS Command Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in 200.17.7.0.139 : patch CommScope Ruckus Unleashed as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.1Critical
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.
Affects
CommScope Ruckus Unleashed prior to 200.15.6.212.14
Patch
Available – fixed in 200.17.7.0.139, 200.15.6.212.14, 10.5.1.0.279
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jul 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 26 Oct 2026.

What to do

AI-suggested

  1. Immediate Steps: Restrict access to the CLI interface to trusted administrators only, using strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise.
  2. Network Segmentation: Isolate management interfaces of Ruckus controllers from general network access, limiting exposure to only necessary management stations.
  3. Monitoring and Logging: Enable detailed logging and monitor CLI access for unusual or unauthorized activity, including attempts to invoke the `.ap_debug.sh` script or other suspicious commands.
  4. Firmware Updates: Although no patches were listed at the time of disclosure, organizations should closely monitor CommScope’s official channels for firmware updates addressing this vulnerability and apply them immediately upon release.
  5. Credential Hygiene: Enforce strong password policies and regularly rotate credentials used for accessing the controllers to minimize the risk of credential theft.
  6. Incident Response Preparation: Develop and test incident response plans specifically for network infrastructure compromise scenarios, including isolating affected devices and forensic analysis.
  7. Vendor Engagement: Engage with CommScope support to obtain guidance, potential workarounds, or early access to patches.
  8. Disable Debug Features: Where possible, disable or restrict access to hidden debug scripts or features not required for normal operations to reduce attack surface.

Description

An issue was discovered in CommScope Ruckus Unleashed prior to 200.15.6.212.14 and 200.17.7.0.139, and in Ruckus ZoneDirector prior to 10.5.1.0.279, where a hidden debug script `.ap_debug.sh` invoked from the restricted CLI does not properly sanitize its input, allowing an authenticated attacker to execute arbitrary commands as root on the controller or specified target.

References

Community reviews

Loading reviews…