Skip to content
IoT

CVE-2026-15315

8.7
High
EPSS 0.30%Patch availableAug 19, 2026

Local auth bypass in Tapo C200 v5 allows admin access and service disruption

common questions

Is CVE-2026-15315 being exploited?

Not confirmed. CVE-2026-15315 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-15315?

CVE-2026-15315 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-15315?

Yes. A fix has been recorded for CVE-2026-15315. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-15315 affect?

CVE-2026-15315 affects TP-Link Tapo C200 (firmware v5). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-15315?

Isolate devices from untrusted LAN, disable remote/admin access, monitor, apply firmware update when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TP-Link Tapo C200 (firmware v5)
impact

Local network attacker can bypass authentication to obtain admin session tokens, perform privileged management actions, and cause temporary DoS.

action required

Immediate action required

affected versions
TP-Link Systems Inc Tapo C120 v1
  • affected< 1.9.3 Build 260521
TP-Link Systems Inc. Tapo C200 v5
  • affected< V5_1.4.6 Build 260709 Rel.27675n

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free