dbcve.org
Tapo C260 FirmwareOperating system · Tp Link

CVE-2026-0652

HIGH · 8.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 1.1.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
On TP-Link Tapo C260 v1, command injection vulnerability exists due to improper sanitization in certain POST parameters during configuration synchronization. An authenticated attacker can execute arbitrary system commands with high impact on confidentiality, integrity and availability. It may cause full device compromise.

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 · moderate confidence

A command injection vulnerability exists in the TP-Link Tapo C260 v1 camera firmware. The issue stems from improper sanitization of POST parameters during the configuration synchronization process, allowing an authenticated attacker to inject and execute arbitrary system commands with root privileges.

MitigationApply vendor-supplied firmware updates immediately. If no patch is available, restrict network access to the device's management interface and enforce strong authentication to limit exposure to authenticated attackers.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 and firmware version
    Access the camera's web interface or use the Tapo app to view device information. Look for the model number (should be C260) and firmware version displayed in the system settings or device status page.
    Affected if The device is a TP-Link Tapo C260 v1 and the firmware version is lower than 1.1.9 (e.g., 1.1.8, 1.1.7, etc.)
  2. Verify configuration synchronization feature accessibility
    Locate the configuration backup/restore or sync feature in the camera's web management interface. This is typically found under Settings, Maintenance, or System settings menus.
    Affected if The configuration synchronization feature is accessible without additional access controls beyond standard authentication
  3. Confirm authentication to the device
    Verify that valid credentials exist for the camera's management interface. The vulnerability requires an authenticated session to exploit.
    Affected if Attacker possesses valid authentication credentials for the Tapo C260 management interface

The environment is affected if the TP-Link Tapo C260 v1 is running firmware version 1.1.8 or lower, the configuration synchronization feature is accessible, and the attacker can obtain valid authentication to the device.

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-supplied firmware updates immediately. If no patch is available, restrict network access to the device's management interface and enforce strong authentication to limit exposure to authenticated attackers.

Recommended fix Moderate confidence

Tapo C260 Firmware version 1.1.9 or later

  1. 1. Identify the current firmware version of the Tapo C260 camera via the Tapo app or web interface.
  2. 2. Download the latest firmware version 1.1.9 or later from the official TP-Link support website (support.tp-link.com).
  3. 3. Access the camera settings through the Tapo app or web interface.
  4. 4. Navigate to the firmware update section and initiate the firmware upgrade process.
  5. 5. Wait for the firmware upload and installation to complete - do not power off the device during the update.
  6. 6. After the device restarts, verify the firmware version has been updated to 1.1.9 or higher.
  7. 7. Confirm the vulnerability is remediated by testing that the previously vulnerable POST parameters are now properly sanitized.
Caveat Firmware updates may temporarily interrupt camera operation; ensure stable power during the upgrade process

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

Fix this in Tapo C260 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0652 — 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-0652 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