Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0651: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in TP-Link Systems Inc. Tapo C260 v1

0
Medium
VulnerabilityCVE-2026-0651cvecve-2026-0651cwe-22
Published: Tue Feb 10 2026 (02/10/2026, 17:27:51 UTC)
Source: CVE Database V5
Vendor/Project: TP-Link Systems Inc.
Product: Tapo C260 v1

Description

A path traversal vulnerability was identified TP-Link Tapo C260 v1, D235 v1 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 19:26:15 UTC

Technical Analysis

CVE-2026-0651 is a path traversal vulnerability identified in TP-Link Tapo C260 v1 and D235 v1 smart camera devices. The flaw stems from improper validation and limitation of pathname inputs in HTTPS GET requests, allowing an attacker on the same local network to craft requests that probe the device's filesystem paths. This vulnerability is classified under CWE-22, which refers to improper limitation of a pathname to a restricted directory, commonly known as path traversal. The attacker can determine the presence or absence of specific files on the device, which could aid in reconnaissance or further targeted attacks. However, the vulnerability does not allow reading file contents, writing files, or executing arbitrary code, limiting its direct impact. The attack vector is network-based (local network), requires no authentication or user interaction, and has a low complexity of attack. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the limited impact on confidentiality and integrity but potential information disclosure. No patches or exploits are currently documented, but the vulnerability is publicly disclosed and assigned a CVE identifier. This issue highlights the importance of strict input validation and access controls in IoT device firmware to prevent unauthorized filesystem probing.

Potential Impact

The primary impact of CVE-2026-0651 is information disclosure through filesystem probing. Attackers on the local network can infer the existence of files, which may reveal device configuration details, firmware versions, or other sensitive metadata. While no direct read, write, or code execution is possible, this reconnaissance capability can facilitate further attacks or targeted exploitation if combined with other vulnerabilities. For organizations deploying these TP-Link devices, especially in sensitive environments, this vulnerability could undermine security by exposing device internals to unauthorized parties. The risk is heightened in environments with weak network segmentation or where local network access is easily obtained, such as public Wi-Fi or poorly secured corporate networks. Although the severity is medium, the vulnerability could contribute to a larger attack chain, increasing overall risk. The lack of available patches means the vulnerability may persist until addressed by the vendor, prolonging exposure.

Mitigation Recommendations

To mitigate CVE-2026-0651, organizations should implement strict network segmentation to isolate TP-Link Tapo devices from untrusted or guest network segments, limiting local network access to authorized users only. Employ network access controls such as VLANs and firewall rules to restrict communication with these devices. Monitor network traffic for unusual HTTPS GET requests targeting device paths indicative of probing attempts. Disable or limit device management interfaces accessible from local networks if not required. Regularly update device firmware and check for vendor patches addressing this vulnerability once available. Consider deploying intrusion detection systems (IDS) capable of detecting path traversal patterns in HTTP/HTTPS traffic. For high-security environments, evaluate alternative devices with stronger security postures or enhanced input validation. Maintain an inventory of affected devices and plan for timely remediation when patches are released.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
TPLink
Date Reserved
2026-01-06T18:19:00.313Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 698b6f014b57a58fa11d3741

Added to database: 2/10/2026, 5:46:41 PM

Last enriched: 3/31/2026, 7:26:15 PM

Last updated: 4/6/2026, 4:07:46 PM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses