Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain access to local network segment
-
ExploitSend crafted local discovery protocol request to device
-
ExecutionDevice responds without authentication
-
ImpactExtract geolocation metadata from response payload
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must be on the same local network segment (adjacent network) as the affected TP-Link Kasa EC70 v4 or EC71 v4 device - for example, connected to the same Wi-Fi access point or LAN. No authentication is required (PR:N per CVSS). The device must be powered on and operational so its local discovery service is responsive. No special non-default configuration is required; the vulnerability exists in the default discovery mechanism. Exploitation is limited by the adjacency requirement: remote internet-based attackers cannot reach the discovery service without first gaining LAN access via another vector (e.g., VPN compromise, rogue device, or physical access). Geolocation data exposure is the only impact; the attacker cannot modify device settings or cause a denial of service through this vector. |
| Impact | The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N) accurately captures the constrained risk profile. The adjacent network requirement (AV:A) is the primary limiting factor: exploitation requires physical or logical presence on the same network segment as the device, ruling out internet-scale opportunistic attacks. The low confidentiality impact (VC:L) reflects geolocation data leakage - sensitive from a privacy standpoint but not a system-compromise class finding. No KEV listing and no public POC have been identified, and EPSS data is not available for this CVE. The vulnerability is real and warrants patching - particularly in enterprise or sensitive-location deployments where physical location disclosure is a meaningful operational security concern - but it does not represent an imminent compromise risk for most consumer deployments. The risk is elevated in environments where insider threat or rogue Wi-Fi client access is a concern. |
| Exploit ScenarioDerived | An attacker connected to the same Wi-Fi or wired LAN segment as a Kasa EC70 or EC71 device crafts a discovery protocol request targeting the device's local advertisement service. The device responds with a payload that includes geolocation metadata - such as coordinates or address data stored by the device - without requiring any credentials. No public exploit code exists, but the attack requires only basic network tooling and knowledge of the discovery protocol format. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 15, 2026
Unauthenticated information disclosure in TP-Link Kasa EC70 v4 and EC71 v4 exposes sensitive geolocation data to any attacker on the same local network segment. The flaw resides in the devices' local discovery mechanism, which returns geolocation-related information in response to crafted network probes without requiring any credentials. Impact is limited to confidentiality; no integrity or availability compromise is possible through this vector. No public exploit exists and no active exploitation has been confirmed.
RemediationAI
The primary remediation is applying the patched firmware provided by TP-Link. Firmware release notes and downloads are available at https://www.tp-link.com/us/support/download/ec71/#Firmware-Release-Notes and https://www.tp-link.com/us/support/download/ec70/v4/#Firmware-Release-Notes; users should update to the latest firmware version listed on those pages. The vendor advisory at https://www.tp-link.com/us/support/faq/5192/ should be consulted for the specific fixed firmware version. As a compensating control prior to patching, isolating these devices on a dedicated IoT VLAN with strict inter-VLAN routing rules will prevent untrusted local network clients from reaching the discovery port - this is architecturally sound regardless of patching. Disabling device discovery features via the Kasa app (if the option exists) may also reduce exposure but should be verified not to break core device functionality.
Affected VersionsENISA
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 affected products are TP-Link Kasa-branded smart devices (CPE: cpe:2.3:a:tp-link_systems_inc.:kasa_ec71_v4 and cpe:2.3:a:tp-link_systems_inc.:kasa_ec70_v4), likely smart cameras or plugs with built-in local network discovery protocols (e.g., mDNS, SSDP, or a proprietary TP-Link discovery protocol). CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) identifies the root cause: the discovery mechanism broadcasts or responds to probes with more information than is necessary, including geolocation metadata that should be restricted. This is a classic over-disclosure in IoT device advertisement protocols, where convenience features expose device context data without access controls.
Know when Kasa Ec70 V4 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
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
Adjacent network vector required; no authentication needed; only low confidentiality impact from geolocation disclosure; no integrity or availability impact.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
An information disclosure vulnerability was identified in TP-Link Kasa EC70 v4 and EC71 v4 in the local discovery mechanism, which exposes sensitive geolocation information without requiring authentication. This issue allows an attacker on the same local network to retrieve geolocation-related data through crafted responses.
The vulnerability impacts confidentiality only, with no evidence of integrity of availability impact.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-44577
GHSA-rccw-h6pm-46g4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB