Skip to main content
Mallory
LowVulnerability

CVE-2025-6243: Built-in Root-Privileged SSH User and Key Exposure in RUCKUS Network Director

Updated 3 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS0.0Low
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2025-6243CWE-798

CVE-2025-6243 is a credential-management vulnerability in RUCKUS Network Director (RND). The platform contains a built-in user account, sshuser, that has root privileges, and both the public and private SSH keys for that account are stored in the account's home directory. Possession of the private key enables SSH authentication as the built-in privileged user. Because the account is pre-existing and highly privileged, the flaw effectively exposes a built-in administrative access path that can be used to obtain shell access on the affected RND server.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker who obtains the embedded private SSH key to authenticate to the affected RND server as a root-privileged built-in user and gain shell access. This can result in full system compromise, including unrestricted administrative control over the appliance, access to sensitive configuration and managed-network data, modification of system state, deployment of additional payloads, and use of the server as a pivot point for further operations.

Mitigation

If you can’t patch tonight, do this now.

Until patched, restrict SSH access to the RND server to tightly controlled management networks and trusted administrators only, disable SSH if operationally feasible, and monitor for any use of the built-in privileged account. Apply strict network segmentation and access controls around the management interface, review authentication logs for anomalous SSH activity, and treat the appliance as potentially compromised if unauthorized access cannot be ruled out. If possible within operational constraints, remove or disable the built-in account and invalidate associated key material pending vendor guidance.

Remediation

Patch, then assume compromise.

Upgrade RUCKUS Network Director to a fixed release. Reported affected versions include RND 4.0.x prior to 4.0.0.47 and RND 4.5.x prior to 4.5.0.51; RND 3.0 is also listed as affected prior to an unspecified patched release. Remove or disable the exposed built-in access path as part of vendor-provided remediation, including replacement of any embedded SSH credentials and keys where applicable. If compromise is suspected, rotate administrative credentials and SSH material, review authorized access, and rebuild or reimage affected systems as necessary.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-6243 exploited in the wild?
As of Aug 24, 2026, Mallory has no reports of CVE-2025-6243 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-6243?
As of Aug 24, 2026, Mallory has found no public exploit for CVE-2025-6243.
Is there a patch for CVE-2025-6243?
Upgrade RUCKUS Network Director to a fixed release. Reported affected versions include RND 4.0.x prior to 4.0.0.47 and RND 4.5.x prior to 4.5.0.51; RND 3.0 is also listed as affected prior to an unspecified patched release.
How severe is CVE-2025-6243?
CVE-2025-6243 has a CVSS score of 0.0 (Low) as of Aug 24, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.