dbcve.org
Tapo C260 FirmwareOperating system · Tp Link

CVE-2026-0653

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 1.1.9 or later.
See remediation →
71/100
Remediation priority · Elevated
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 and D235 v1, a guest‑level authenticated user can bypass intended access restrictions by sending crafted requests to a synchronization endpoint. This allows modification of protected device settings despite limited privileges. An attacker may change sensitive configuration parameters without authorization, resulting in unauthorized device state manipulation but not full code execution.

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

A vertical privilege escalation vulnerability in TP-Link Tapo C260 v1 and D235 v1 allows guest-level authenticated users to bypass access controls on a synchronization endpoint. By sending crafted requests, attackers can modify protected device settings that should require higher privileges, enabling unauthorized device state manipulation without achieving full code execution.

MitigationApply vendor firmware updates from TP-Link when available; until then, restrict guest-level account access and monitor for unauthorized configuration changes.

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
None
Integrity
High
Availability
None

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

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 TP-Link Tapo app or device web interface to confirm the exact model number is Tapo C260 v1 or D235 v1
    Affected if Device is a Tapo C260 v1 or D235 v1
  2. Check firmware version
    In the Tapo app, go to Device Settings > Device Info to view the current firmware version. For C260, compare against 1.1.9
    Affected if Firmware version is below 1.1.9 for C260 (version range for D235 not specified)
  3. Verify guest account status
    In the Tapo app, check Device Settings > Guest Network or account management to see if guest-level accounts are enabled
    Affected if Guest accounts are enabled and active on the device
  4. Audit recent configuration changes
    Review device logs or configuration history for unexpected changes to protected settings (such as network configuration, motion detection settings, or automation rules) that were not made by an admin account
    Affected if Configuration changes exist that were not initiated by an administrator-level account

The device is affected if it is a Tapo C260 v1 (firmware below 1.1.9) or D235 v1 with guest accounts enabled, and unauthorized configuration changes are present in the logs.

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 from TP-Link when available; until then, restrict guest-level account access and monitor for unauthorized configuration changes.

Recommended fix Moderate confidence

Firmware version 1.1.9 or later for Tapo C260 (and corresponding fix for D235 v1)

  1. 1. Access the Tapo C260 device through its mobile app or web interface
  2. 2. Navigate to the device settings or firmware update section
  3. 3. Check the current firmware version to confirm it is below 1.1.9
  4. 4. Download firmware version 1.1.9 or later from the official TP-Link support website (www.tp-link.com)
  5. 5. Follow TP-Link's standard firmware upgrade procedure to apply the update
  6. 6. After upgrading, verify the new firmware version is 1.1.9 or higher
  7. 7. Confirm the access control vulnerability is resolved by testing with a guest-level account

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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