CVE-2026-0653: Insecure Access Control on TP-Link Tapo D235 and C260
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.
Security readout for executives and security teams
Plain-English summary
A user with only guest access to a TP-Link Tapo C260 v1 or D235 v1 may alter settings that should be protected. This could disrupt operation or weaken intended configuration controls. The issue does not provide full code execution, and the supplied evidence does not establish active exploitation.
Executive priority
Prioritize identification and updating of affected cameras and doorbells, especially where guest accounts exist or management interfaces are broadly reachable. Treat as high priority because unauthorized changes can affect device integrity and availability. Escalate immediately if unexplained configuration changes are found.
Technical view
CVE-2026-0653 is a CWE-284 access-control flaw in a synchronization endpoint. Crafted requests from a guest-level authenticated account can bypass authorization and modify protected settings. CVSS 4.0 is 7.2: network-accessible, low complexity, no user interaction, with high integrity and availability impact but limited confidentiality impact.
Likely exposure
Exposure requires network access to the affected device interface and valid guest-level authentication. Confirmed scope is limited to Tapo C260 v1 and D235 v1. The bundle does not identify exact vulnerable or fixed firmware versions, and its structured version data is ambiguous.
Exploitation context
The attack requires an authenticated guest account but no user interaction. It enables unauthorized configuration changes, not arbitrary code execution. The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation or a public exploit.
Researcher notes
The supplied affected-version entries contain version “0” with a default status of unaffected, while the narrative identifies C260 v1 and D235 v1. Exact firmware boundaries therefore remain unclear. Use the vendor advisory and model-specific download pages as the authoritative remediation references; avoid assuming every firmware release is vulnerable.
Mitigation direction
Inventory Tapo C260 v1 and D235 v1 devices and record their installed firmware.
Check TP-Link's advisory and download pages for the applicable fixed firmware.
Apply vendor-provided firmware through the supported update process when confirmed.
Until updated, restrict management access and remove unnecessary guest-level accounts.
Monitor protected settings for unexpected changes.
Validation and detection
Verify each device's exact model, hardware revision, and firmware version.
Compare installed firmware with TP-Link's current advisory and model download page.
Review guest accounts and confirm each remains necessary.
Check configuration history or logs for unexplained protected-setting changes.
After updating, confirm normal operation and intended guest-access restrictions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.