<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: tapo c220 firmware</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2026-1315: By sending crafted files to the firmware update endpoint of Tapo C220 v1 and C520WS v2, the device terminates </title><link>https://patchthecve.com/cve/CVE-2026-1315.html</link><guid>https://patchthecve.com/cve/CVE-2026-1315.html</guid><pubDate>Wed, 17 Jun 2026 10:15:35 +0000</pubDate><description>HIGH 7.5: 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 i</description></item><item><title>CVE-2026-0919: The HTTP parser of Tapo C210 v3, C220 v1 and C520WS v2 cameras improperly handles requests containing an exces</title><link>https://patchthecve.com/cve/CVE-2026-0919.html</link><guid>https://patchthecve.com/cve/CVE-2026-0919.html</guid><pubDate>Wed, 17 Jun 2026 10:11:37 +0000</pubDate><description>HIGH 7.5: 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 forc</description></item><item><title>CVE-2026-0918: The Tapo C100 v5, C220 v1 and C520WS v2 cameras’ HTTP service does not safely handle POST requests containing </title><link>https://patchthecve.com/cve/CVE-2026-0918.html</link><guid>https://patchthecve.com/cve/CVE-2026-0918.html</guid><pubDate>Wed, 17 Jun 2026 10:11:37 +0000</pubDate><description>HIGH 7.5: 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. The resulting failed memory allocation triggers a NULL pointer dereference, causing the main service process to crash. An unauthenticated attacker</description></item></channel></rss>