# CVE-2025-46121: Other in n/a

> A format string vulnerability in Ruckus Unleashed allows remote attackers to execute arbitrary code on the controller via crafted DHCP hostnames or admin requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-6c72-qmmh-6499

## What is CVE-2025-46121?

CVE-2025-46121 is a critical vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in CommScope Ruckus Unleashed prior to 200.15.6.212.14 and 200.17.7.0.139, where the functions `stamgr_cfg_adpt_addStaFavourite` and `stamgr_cfg_adpt_addStaIot` pass a client hostname directly to snprintf as the format string. A remote attacker can exploit this flaw either by sending a crafted request to the authenticated endpoint `/admin/_conf.jsp`, or without authentication and without direct network access to the controller by spoofing the MAC address of a favourite station and embedding malicious format specifiers in the DHCP hostname field, resulting in unauthenticated format-string processing and arbitrary code execution on the controller.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2025-46121?

It affects 2 products.


Products: Ruckuswireless Ruckus Unleashed, Ruckuswireless Ruckus Zonedirector.

## How do I fix CVE-2025-46121?

No fix has been published for CVE-2025-46121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-46121 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46121 exists.

## Other vulnerabilities in n/a

- [CVE-2025-46120](https://insights.sbomify.com/CVE-2025-46120/): Path traversal in n/a (critical 9.8)
- [CVE-2025-46117](https://insights.sbomify.com/CVE-2025-46117/): Command injection in n/a (critical 9.1)
- [CVE-2025-46122](https://insights.sbomify.com/CVE-2025-46122/): Command injection in n/a (critical 9.1)
- [CVE-2025-46116](https://insights.sbomify.com/CVE-2025-46116/): Privilege escalation in n/a (high 8.8)
- [CVE-2025-46123](https://insights.sbomify.com/CVE-2025-46123/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46121 and fix it if it is affected.

What it is: CVE-2025-46121 is a critical vulnerability in n/a, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46121 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46121/ (Markdown: https://insights.sbomify.com/CVE-2025-46121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46121
- OSV: https://osv.dev/vulnerability/CVE-2025-46121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46121/
Summaries are generated and may contain mistakes; the official description above is the record.