# CVE-2026-86149: Tenda CP3 NetCheckPing.cpp os command injection

> Remote attackers can execute arbitrary OS commands on Tenda CP3 cameras via the NetCheckPing interface, requiring immediate attention from device owners.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-qh73-x3c2-xph4

## What is CVE-2026-86149?

CVE-2026-86149 is a critical command injection vulnerability in Tenda CP3, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.

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

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


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

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

## Is CVE-2026-86149 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86149 is a critical command injection vulnerability in Tenda CP3, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86149 in the wild and no public exploit code.

Affected product: Tenda CP3. 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-86149/ (Markdown: https://insights.sbomify.com/CVE-2026-86149/index.md)
```

## Sources

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

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