CyberSecBulletin
CVE-2026-0651NVD status: Modified

Tapo C260 v1: Improper Limitation of a Pathname to a Restricted Directory

Published Updated By the CyberSecBulletin desk

CVE-2026-0651 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Tapo C260 v1 from TP-Link, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 1.1.9 Build 251226 Rel.55870n as the first without the flaw, so updating Tapo C260 v1 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.8% chance of exploitation within 30 days, higher than 57% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Tapo C260 v1 to 1.1.9 Build 251226 Rel.55870n or a later version.
  2. Update Tapo D235 v1 to 1.2.2 Build 260210 Rel.27165n or a later version.
  3. Update Tapo C520WS v2.6 to 1.2.4 Build 260326 Rel.24666n or a later version.
  4. Read the advisory on tp-link.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkTapo C260 v1before 1.1.9 Build 251226 Rel.55870n1.1.9 Build 251226 Rel.55870n
TP-LinkTapo D235 v1before 1.2.2 Build 260210 Rel.27165n1.2.2 Build 260210 Rel.27165n
TP-LinkTapo C520WS v2.6before 1.2.4 Build 260326 Rel.24666n1.2.4 Build 260326 Rel.24666n
TP-LinkTapo C211 v2before 1.5.4 Build 260702 Rel.7078n1.5.4 Build 260702 Rel.7078n
TP-LinkTapo C260 Firmwarebefore 1.1.91.1.9

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.06.9MediumCNA
CVSS 3.17.8HighNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Tapo C260 v1

All Tapo C260 v1 vulnerabilities

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.