dbcve.org
Tapo C260 FirmwareOperating system · Tp Link

CVE-2026-0651

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 1.1.9 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TP-Link Tapo C260, D235, and C520WS devices contain a path traversal vulnerability in their HTTP server. The server normalizes paths before fully decoding URL-encoded input and falls back to the raw path when normalization fails. Attackers can bypass directory restrictions by supplying crafted URL-encoded traversal sequences (e.g., %2e%2e%2f) to access files outside the web root.

MitigationApply vendor firmware updates when available; until then, restrict network access to the devices and consider network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tapo C260 FirmwareOperating system
Affected:< 1.1.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device management interface or check the device label to confirm the exact model (C260, D235, or C520WS)
    Affected if The device is a TP-Link Tapo C260, D235, or C520WS
  2. Check C260 firmware version
    For Tapo C260: Navigate to Device Settings > Firmware Version in the Tapo app, or access the device's web interface and look for the firmware version displayed in the system or about section
    Affected if The firmware version is lower than 1.1.9 (e.g., 1.1.8, 1.1.7, etc.)
  3. Check D235 and C520WS firmware version
    For D235 or C520WS: Navigate to Device Settings > Firmware Version in the Tapo app, or access the device's web interface and look for the firmware version displayed in the system or about section
    Affected if No fixed version is specified for these models; any version may be affected until vendor confirms otherwise
  4. Verify HTTP server is accessible
    Attempt to access the device's HTTP web interface by entering the device's IP address in a web browser (e.g., http://[device-ip])
    Affected if The HTTP server responds and accepts requests, indicating the vulnerable endpoint is exposed on the network

You are affected if you have a Tapo C260 with firmware below 1.1.9, or any D235/C520WS model with an accessible HTTP server, as the path traversal vulnerability can be exploited to access files outside the web root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.9 or later
Fixed in 1.1.9
Interim mitigation

Apply vendor firmware updates when available; until then, restrict network access to the devices and consider network segmentation to limit exposure.

Recommended fix Moderate confidence

Firmware version 1.1.9

  1. Locate the TP-Link Tapo C260 device in your network and access its management interface
  2. Navigate to the Firmware Upgrade section in the device settings
  3. Check the current firmware version to confirm it is below 1.1.9
  4. Download the firmware version 1.1.9 or later from the official TP-Link support website (www.tp-link.com)
  5. Upload the firmware file through the device's web interface or use the Tapo mobile app to apply the update
  6. Wait for the firmware installation to complete and the device to reboot
  7. Verify the firmware version has been updated to 1.1.9 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapo C260 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0651 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data