dbcve.org
Tapo C220 FirmwareOperating system · Tp Link

CVE-2026-1315

HIGH · 7.5 CVSS v3.1 Published 2026-01-27
Fix available
A fix is available. Upgrade to 1.2.3 / 1.4.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
By sending crafted files to the firmware update endpoint of Tapo C220 v1 and C520WS v2, the device terminates core system services before verifying authentication or firmware integrity. An unauthenticated attacker can trigger a persistent denial of service, requiring a manual reboot or application initiated restart to restore normal device operation.

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 Tapo C220 v1 and C520WS v2 cameras have a vulnerability in their firmware update endpoint where sending crafted files causes core system services to terminate before any authentication or firmware integrity verification occurs. This allows unauthenticated attackers to cause a persistent denial of service that requires manual or application-initiated reboot to recover.

MitigationApply vendor firmware patches when available; as an interim control, restrict network access to the firmware update endpoint via firewall rules or network segmentation to prevent unauthenticated external attackers from reaching the update interface.

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 C220 FirmwareOperating system
Affected:< 1.4.2
Tapo C520ws FirmwareOperating system
Affected:< 1.2.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your Tapo camera model
    Locate the model number printed on the device label or check in the Tapo mobile app under Device Settings > Device Info
    Affected if The device is a Tapo C220 or Tapo C520WS model
  2. Check the installed firmware version on C220
    Open the Tapo app, select the C220 camera, go to Device Settings > Device Info, and note the Firmware version displayed
    Affected if The firmware version is lower than 1.4.2 (for example, 1.4.1, 1.4.0, or earlier)
  3. Check the installed firmware version on C520WS
    Open the Tapo app, select the C520WS camera, go to Device Settings > Device Info, and note the Firmware version displayed
    Affected if The firmware version is lower than 1.2.3 (for example, 1.2.2, 1.2.1, or earlier)
  4. Assess network exposure of the firmware update endpoint
    Review your network firewall or router settings to determine if the camera is accessible from external networks (WAN) or untrusted VLANs on ports used for firmware updates
    Affected if The device firmware update interface is reachable from untrusted network segments or the internet without network segmentation

You are affected if you own a Tapo C220 with firmware < 1.4.2 or a Tapo C520WS with firmware < 1.2.3, and the device firmware update endpoint is network-accessible to untrusted parties.

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.2.3 / 1.4.2 or later
Fixed in 1.2.31.4.2
Interim mitigation

Apply vendor firmware patches when available; as an interim control, restrict network access to the firmware update endpoint via firewall rules or network segmentation to prevent unauthenticated external attackers from reaching the update interface.

Recommended fix High confidence

Tapo C220: upgrade to firmware 1.4.2 or later; Tapo C520ws: upgrade to firmware 1.2.3 or later

  1. Identify the Tapo camera model (C220 or C520ws) in your environment
  2. Access the Tapo mobile app or web interface for the affected device
  3. Navigate to the device settings or firmware update section
  4. Check the current firmware version to confirm it is vulnerable (C220 < 1.4.2 or C520ws < 1.2.3)
  5. Download the latest firmware update from TP-Link's official support page for your specific model
  6. Apply the firmware update through the app or web interface
  7. Verify the update was successful by checking the new firmware version number (1.4.2 or later for C220; 1.2.3 or later for C520ws)
  8. Restart the device if not automatically restarted after the update

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

Fix this in Tapo C220 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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