# CVE-2026-17176: OS Command Injection Vulnerability in Deco Devices

> Adjacent network attackers can execute arbitrary root commands on TP-Link Deco devices via crafted UDP packets, leading to full device compromise.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g92m-rv6c-v268

## What is CVE-2026-17176?

CVE-2026-17176 is a high-severity command injection vulnerability in TP-Link Systems Inc. Deco BE11000 V2, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An OS
command injection vulnerability in the TDDP module of Deco BE11000 and Deco M9 Plus allows an
adjacent network attacker to execute arbitrary commands with root privileges by
sending a crafted UDP packet.

Successful exploitation may lead to complete
device compromise, including unauthorized command execution, modification of
device settings, and loss of confidentiality, integrity, and availability

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

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


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

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

## Is CVE-2026-17176 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17176 is a high-severity command injection vulnerability in TP-Link Systems Inc. Deco BE11000 V2, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17176 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Deco BE11000 V2. 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-17176/ (Markdown: https://insights.sbomify.com/CVE-2026-17176/index.md)
```

## Sources

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

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