CyberSecBulletin
CVE-2026-0919NVD status: Modified

The HTTP parser of Tapo C210 v3, C220 v1 and C520WS v2 cameras improperly handles requests…

Published Updated By the CyberSecBulletin desk

CVE-2026-0919 is a high-severity improper input validation vulnerability in Tapo C220 v1 from TP-Link, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.4.2 Build 251112 as the first without the flaw, so updating Tapo C220 v1 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.61% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Tapo C220 v1 to 1.4.2 Build 251112 or a later version.
  2. Update Tapo C520WS v2 to 1.2.3 Build 251114 or a later version.
  3. Update Tapo C210 v3 to 1.2.6 Build 260328 or a later version.
  4. Read the advisory on tp-link.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkTapo C220 v1before 1.4.2 Build 2511121.4.2 Build 251112
TP-LinkTapo C520WS v2before 1.2.3 Build 2511141.2.3 Build 251114
TP-LinkTapo C210 v3before 1.2.6 Build 2603281.2.6 Build 260328
TP-LinkTapo C220 Firmwarebefore 1.4.21.4.2
TP-LinkTapo C520ws Firmwarebefore 1.2.31.2.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.07.1HighCNA
CVSS 3.17.5HighNVD

Official description

The HTTP parser of Tapo C210 v3, C220 v1 and C520WS v2 cameras improperly handles requests containing an excessively long URL path. An invalid‑URL error path continues into cleanup code that assumes allocated buffers exist, leading to a crash and service restart. An unauthenticated attacker can force repeated service crashes or device reboots, causing denial of service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Tapo C220 v1

All Tapo C220 v1 vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.