Persistent service outage via pre-verification service termination
Published Jan 27, 2026 · Updated Jan 27, 2026
Improper input validation in Tapo C220 v1 and C520WS v2 allows remote attackers to cause a persistent service outage via crafted firmware files. The firmware update endpoint stops core system services before it verifies request authentication or the integrity of the supplied firmware file. An attacker on an adjacent network needs no credentials or user interaction, and recovery requires a manual reboot or an application-initiated restart.
Summary
What happened
Improper input validation in Tapo C220 v1 and C520WS v2 allows remote attackers to cause a persistent service outage via crafted firmware files. The firmware update endpoint stops core system services before it verifies request authentication or the integrity of the supplied firmware file. An attacker on an adjacent network needs no credentials or user interaction, and recovery requires a manual reboot or an application-initiated restart.
The record
- CVE
- CVE-2026-1315
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Tapo C520WS
- Classifications
- CWE-20, CAPEC-23, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.2.3 Build 251114
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo