Quick answers
- Is CVE-2026-0651 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0651 being exploited in the wild.
- How severe is CVE-2026-0651?
- High severity, with a CVSS score of 7.8, published 10 February 2026.
- Which products and versions are affected?
- TP-Link Tapo C211 v2; TP-Link Tapo C520WS v2.6; TP-Link Tapo D235 v1; TP-Link Tapo C260 v1.
- Is there a fix for CVE-2026-0651?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-0651 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-0651?
- Check whether you run TP-Link Tapo C211, TP-Link Tapo C520WS, TP-Link Tapo D235 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the HTTP server's handling of GET requests across multiple Tapo camera models. The server performs path normalization before fully decoding URL-encoded input and falls back to the raw path when normalization fails, allowing attackers to bypass directory restrictions using crafted, URL-encoded traversal sequences. Authenticated users can disclose sensitive system files and credentials; unauthenticated attackers can access non-sensitive static assets. Network access to the camera's HTTP server is required; no user interaction is needed once the request is crafted. Patches are expected from TP-Link for the affected firmware versions.
Affected products
- TP-Link Tapo C260 v1
- TP-Link Tapo D235 v1
- TP-Link Tapo C211 v2
- TP-Link Tapo C520WS v2.6
Timeline
- 2026-02-10: disclosed