# CVE-2026-71961: Cudy WR3000 2.0 OS Command Injection via Mesh MQTT Command Handler

> Authenticated attackers can execute arbitrary root commands on Cudy WR3000 routers via unsanitized input in the mesh MQTT command handler.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-8jmp-g7g6-gf45

## What is CVE-2026-71961?

CVE-2026-71961 is a high-severity command injection vulnerability in Shenzhen Cudy Technology Co., Ltd. WR3000 2.0, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cudy WR3000 2.0 running firmware before 2.5.24 contains an OS command injection vulnerability that allows authenticated attackers to execute arbitrary OS commands with root privileges by sending unsanitized input through the mesh MQTT command interface. The sync_command binary forwards unsanitized input directly to a shell execution sink in command.lua, enabling attackers with access to the MQTT broker to exploit the default-enabled command execution path to achieve full root-level system compromise.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-71961?


## How do I fix CVE-2026-71961?

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

## Is CVE-2026-71961 being exploited?

There is no known exploitation of CVE-2026-71961 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71961 and fix it if it is affected.

What it is: CVE-2026-71961 is a high-severity command injection vulnerability in Shenzhen Cudy Technology Co., Ltd. WR3000 2.0, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71961 in the wild and no public exploit code.

Affected product: Shenzhen Cudy Technology Co., Ltd. WR3000 2.0. 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-2026-71961/ (Markdown: https://insights.sbomify.com/CVE-2026-71961/index.md)
```

## Sources

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

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