Device reboot via oversized Authorization header
Published Jun 2, 2026 · Updated Jun 2, 2026
Stack-based buffer overflow in TP-Link Tapo C200 v5 before 1.4.4 Build 260527 Rel.28339n allows remote attackers to reboot the camera. The RTSP authentication handler accepts an oversized Authorization header without enforcing the destination stack buffer's length boundary. Adjacent-network access is required; no credentials or user interaction are needed, and exploitation interrupts live video and management access until restart.
Summary
What happened
Stack-based buffer overflow in TP-Link Tapo C200 v5 before 1.4.4 Build 260527 Rel.28339n allows remote attackers to reboot the camera. The RTSP authentication handler accepts an oversized Authorization header without enforcing the destination stack buffer's length boundary. Adjacent-network access is required; no credentials or user interaction are needed, and exploitation interrupts live video and management access until restart.
The record
- CVE
- CVE-2026-1871
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- Tapo C200
- Classifications
- CWE-121, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 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.4.4 Build 260527 Rel.28339n
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.
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