# CVE-2026-0651: Path Traversal on TP-Link Tapo D235, C211, C520WS and C260 via Local https

> Authenticated attackers can exploit a path traversal flaw in TP-Link Tapo cameras to read sensitive system files and credentials via crafted URL-encoded requests.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-c348-hjj9-x39v

## What is CVE-2026-0651?

CVE-2026-0651 is a medium-severity path traversal vulnerability in TP Link Systems Inc. Tapo C211 v2, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A path traversal vulnerability was identified TP-Link Tapo C260 v1, D235 v1, C211 v2 and C520WS v2.6 within the HTTP server’s handling of GET requests. The server performs path normalization before fully decoding URL encoded input and falls back to using the raw path when normalization fails. An attacker can exploit this logic flaw by supplying crafted, URL encoded traversal sequences that bypass directory restrictions and allow access to files outside the intended web root. 

Successful exploitation may allow authenticated attackers to get disclosure of sensitive system files and credentials, while unauthenticated attackers may gain access to non-sensitive static assets.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Tp-Link Tapo C260 Firmware.

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

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

## Is CVE-2026-0651 being exploited?

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

Public exploit code:

- PoC exploit chain for TP-Link Tapo C260 camera — CVE-2026-0651/0652/0653. Research by @spaceraccoon. (github_poc): https://github.com/l0lsec/tapo-c260-rce

## Other vulnerabilities in TP Link Systems Inc. Tapo C211 v2

- [CVE-2026-0652](https://insights.sbomify.com/CVE-2026-0652/): Remote Code Execution on TP-Link Tapo C260 by Guest User (high 8.7)
- [CVE-2026-0653](https://insights.sbomify.com/CVE-2026-0653/): Insecure Access Control on TP-Link Tapo D235 and C260 (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0651 is a medium-severity path traversal vulnerability in TP Link Systems Inc. Tapo C211 v2, published on 10 Feb 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-0651 in the wild and no public exploit code.

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

## Sources

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

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