Skip to main content

TP-Link Tapo Camera EUVDEUVD-2026-90981

| CVE-2026-78577 MEDIUM
Missing Authentication for Critical Function (CWE-306)
2026-10-01 TPLink GHSA-7ch5-88j9-f3v7
5.3
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent LAN/Wi-Fi access
  2. Exploit
    Invoke unauthenticated HTTPS scan action
  3. Execution
    Camera returns AP metadata
  4. Impact
    Disclose wireless topology (SSID/BSSID/encryption)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to be on the same local network segment as the camera (CVSS AV:A, adjacent) and targets the HTTPS onboarding scan function specifically AFTER the camera has completed initial setup. No authentication is required (PR:N) and no user interaction is needed (UI:N) against affected Tapo C120 v1 and C200 V5 units. The primary limiting factor is the adjacency requirement - the attacker must already have local network access (wired LAN or associated Wi-Fi), so the flaw is not remotely exploitable from the internet; impact is further limited to disclosure of wireless-environment metadata, with no code execution, credential theft, or video access.

Impact

This is a genuine but low-to-moderate priority issue, not a critical one. The CVSS 4.0 base score of 5.3 (vector AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N) accurately reflects the profile: adjacent-network attack vector (not internet-routable), low complexity, no privileges, no user interaction, but only LOW confidentiality impact and zero integrity or availability impact. The vulnerability (CWE-306, missing authentication) exposes wireless-environment metadata rather than credentials, firmware, or video streams, so the technical impact is information disclosure of relatively low sensitivity. No EPSS score, no CISA KEV listing, and no public POC were provided in the input - exploitation status is therefore 'no public exploit identified at time of analysis.' There is no conflict between the CVSS vector and the description: both consistently indicate an unauthenticated attacker already present on the same local wireless/LAN segment. The low EPSS/KEV absence combined with the adjacent-only vector and low-value payoff suggests this is unlikely to see widespread automated exploitation; realistic abuse requires an attacker already positioned on the victim's network, which bounds the real-world risk well below the raw severity of many network-facing authentication bypasses.

Exploit ScenarioDerived

An attacker who has gained a foothold on the same local network as the camera (e.g., a guest Wi-Fi user or a compromised IoT device) sends the unauthenticated HTTPS onboarding scan request to a Tapo C120 v1 or C200 V5 after its initial setup. The camera responds with nearby access-point metadata - SSIDs, BSSIDs, authentication/encryption modes, and signal strength - letting the attacker map the surrounding wireless topology. No public exploit code is identified at time of analysis; exploitation requires only low complexity and no authentication once network-adjacent.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Unauthenticated devices on the same local network segment as a TP-Link Tapo C120 v1 or Tapo C200 V5 camera can invoke the HTTPS onboarding scan function and pull back metadata about nearby wireless access points, including SSIDs, BSSIDs, authentication and encryption modes, and signal-strength readings (CWE-306, missing authentication for a critical function). The flaw is only reachable after the camera has completed initial setup and requires the attacker to already have adjacent-network access (CVSS:4.0 AV:A/PR:N/UI:N, base 5.3; our own assessment scores it CVSS:3.1 3.1 AV:A/AC:L/PR:N/UI:N with C:L only), so it is not internet-exploitable and yields reconnaissance-grade wireless topology data rather than code execution, credential theft, or camera/video access. There is no KEV listing and no public exploit identified at time of analysis, and TP-Link has published firmware updates for both hardware revisions. This is a genuine but low-to-moderate priority issue, not a critical one, and the practical risk depends entirely on how hostile or shared the camera's LAN/Wi-Fi segment is.

RemediationAI

Apply the vendor firmware update for the exact hardware revision: owners of Tapo C200 V5 should pull the latest firmware from the TP-Link C200 V5 download page (https://www.tp-link.com/us/support/download/tapo-c200/v5/#Firmware-Release-Notes or the /en/ equivalent) and Tapo C120 v1 users should do the same from the C120 v1.26 download page (https://www.tp-link.com/us/support/download/tapo-c120/v1.26/#Firmware-Release-Notes), with TP-Link's FAQ at https://www.tp-link.com/us/support/faq/5321/ covering the advisory details; patch status is 'Patch available per vendor advisory' rather than a specific fix version number, so verify the installed build against the release notes rather than assuming a particular version string. Where immediate patching is not possible, the only meaningful compensating control is isolation, because the vulnerable scan action cannot be disabled post-setup from the camera UI - place the cameras on a dedicated IoT VLAN or guest SSID that is segmented from user workstations, phones, and servers, which removes the adjacent-network foothold the attack requires but costs you direct LAN access to the cameras for local streaming and management. Client isolation on the camera's SSID is a cheaper partial mitigation but its effectiveness depends on the AP and can break the Tapo app's local discovery; blocking the onboarding/HTTPS scan port at the AP or on a host firewall is another option, though it may impair legitimate re-provisioning or Wi-Fi rescan features. Note that strong WPA2/WPA3 keys, MAC filtering, and disabling remote/internet access do not address this issue - the attacker must already hold valid local network access, so network segmentation is the control that actually matters, and there is no public exploit identified at time of analysis, which lowers urgency but not the value of patching.

Affected VersionsENISA

Tapo C120 v1 0 <V1_1.9.4 Build 260813 Rel.79754n
Tapo C200 v5 0 <V5_1.4.6 Build 260709 Rel.27675n

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The defect sits in the HTTPS-based onboarding/commissioning workflow that Tapo cameras expose for the initial Wi-Fi provisioning step - the same routine a mobile app uses to enumerate nearby access points so the camera can be joined to a network. That scan action lacks any authentication or pairing-token check (CWE-306), so after setup is complete the endpoint remains callable by any host that can reach it on the local segment. The information returned is standard 802.11 beacon/probe-response metadata: SSID, BSSID, supported authentication and cipher suites (open/WPA2/WPA3, TKIP/CCMP), and RSSI values. Individually this is low-sensitivity, but in aggregate it maps the surrounding wireless topology and can be used to enumerate hidden or non-broadcast SSIDs, fingerprint AP vendors by BSSID OUI, correlate camera placement with physical location via signal strength, and support follow-on attacks such as evil-twin or deauthentication campaigns against weaker networks in range. Affected product identities in the CPE data are cpe:2.3:a:tp-link_systems_inc.:tapo_c200_v5:*:*:*:*:*:*:*:* and cpe:2.3:a:tp-link_systems_inc.:tapo_c120_v1:*:*:*:*:*:*:*:*, i.e. the C200 hardware revision v5 and the C120 revision v1. The adjacent-network vector (AV:A) with no privileges and no user interaction is the defining characteristic: confidentiality-only, low impact, with no integrity or availability effect on the camera itself.

Know when Tapo C120 V1 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Adjacent network access with no auth or interaction (AV:A/AC:L/PR:N/UI:N); only low-sensitivity metadata is disclosed, so C:L and I:N/A:N.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Tapo C120 v1 and C200 V5 contain a vulnerability in the HTTPS onboarding scan function due to missing authentication. After initial setup, an unauthenticated attacker on the same local network can invoke the scan action and retrieve nearby wireless access-point metadata, including SSIDs, BSSIDs, authentication and encryption modes, and signal-strength information.

Successful exploitation may disclose information about the wireless environment surrounding the camera, allowing an attacker to learn elements of the local wireless topology.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Medium
popular consumer TP-Link smart cameras, but specific affected models/firmware
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy