CVE-2026-0651: Path Traversal on TP-Link Tapo D235, C211, C520WS and C260 via Local https
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.
Security readout for executives and security teams
Plain-English summary
Certain TP-Link Tapo cameras may expose files outside their intended web directory when processing specially encoded local HTTPS requests. An authenticated nearby attacker could potentially obtain sensitive system files or credentials; an unauthenticated attacker may access non-sensitive static files. The supplied evidence does not indicate code execution or file modification.
Executive priority
Address during the next prioritized firmware and network-hardening cycle, accelerating for cameras on shared, guest-accessible, or weakly segmented networks. Credential disclosure could enable broader compromise, but the evidence supports moderate—not critical—urgency because access is adjacent-network scoped and active exploitation is not established.
Technical view
CVE-2026-0651 is a CWE-22 path traversal flaw in GET request handling. The HTTP server normalizes paths before completely URL-decoding them and may revert to the raw path after normalization failure. This can bypass web-root restrictions. CVSS 4.0 is 6.9, with adjacent-network access, low complexity, low privileges, and high confidentiality impact.
Likely exposure
Potentially exposed assets are Tapo C260 v1, D235 v1, C211 v2, and C520WS v2.6 cameras whose local HTTPS service is reachable from an attacker-accessible adjacent network. The supplied affected-version records contain ambiguous version value "0" and default status "unaffected," so exact vulnerable firmware boundaries require vendor confirmation.
Exploitation context
The supplied record does not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires access to the device's local HTTPS service. Sensitive-file or credential disclosure is described for authenticated attackers; unauthenticated impact is limited in the source description to non-sensitive static assets.
Researcher notes
The impact is confidentiality-focused: no vulnerable-component integrity or availability impact is scored. Scope includes limited downstream confidentiality impact. Exact affected and fixed firmware versions are not present in the supplied bundle, while its structured affected entries conflict with the narrative; validate boundaries directly against TP-Link guidance before declaring assets vulnerable or remediated.
Mitigation direction
Inventory the named camera models, hardware revisions, installed firmware, and local HTTPS reachability.
Review TP-Link FAQ 4960 and each model's firmware page for the applicable corrected release.
Install vendor-provided firmware after confirming model, hardware revision, region, and release applicability.
Restrict camera management access to trusted administrative networks and authorized users.
Prevent untrusted or guest networks from reaching camera HTTPS management services.
Validation and detection
Confirm each camera's exact model, hardware revision, region, and installed firmware version.
Compare installed firmware against the applicable TP-Link release notes and advisory.
Verify untrusted network segments cannot reach the cameras' local HTTPS service.
Review available HTTP logs or monitoring for unusual encoded GET requests and unexpected file access.
After updating, confirm normal camera operation and management-network restrictions remain effective.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.