# CVE-2026-86148: Tenda CP3 Kylin system.c SystemAsh os command injection

> Remote attackers can execute arbitrary OS commands via the AlarmVoiceURL argument in the SystemAsh function of the Tenda CP3 camera.

- **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-38rg-j8xg-2m77

## What is CVE-2026-86148?

CVE-2026-86148 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 security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack 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-86148?


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

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

## Is CVE-2026-86148 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86148 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-86148 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-86148/ (Markdown: https://insights.sbomify.com/CVE-2026-86148/index.md)
```

## Sources

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

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