Login Request a demo
High severity · published Jan 27, 2026
CVE-2026-0919
The HTTP parser of Tapo C210 v3, C220 v1 and C520WS v2 cameras improperly handles requests containing an excessively long URL path
7.5
CVSS
0.6%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
None
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.6% · higher than 49% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
TC
Tapo C220 Firmware · Tp-link
before 1.4.2 · source: NVD
TC
Tapo C520ws Firmware · Tp-link
before 1.2.3 · source: NVD
Affected product
TC
Tapo C220 Firmware
Tp-link
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-0919
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-0919
www.tp-link.com
https://www.tp-link.com/en/support/download/tapo-c210/v3/
Product
https://www.tp-link.com/en/support/download/tapo-c220/v1/
Product
https://www.tp-link.com/en/support/download/tapo-c520ws/v2/
www.tp-link.com
https://www.tp-link.com/us/support/download/tapo-c210/v3/
Product
https://www.tp-link.com/us/support/download/tapo-c220/v1.60/
Product
https://www.tp-link.com/us/support/download/tapo-c520ws/v2/
More from Tapo C220 Firmware
7.5
CVE-2026-1315
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…
7.5
CVE-2026-0918
The Tapo C100 v5, C220 v1 and C520WS v2 cameras’ HTTP service does not safely handle POST requests containing an excessively large Content-Length header