cve.bz

CVE-2026-108473 tp-link systems inc.

8.7 highEPSS 0.3%

High (8.7) in tp-link systems inc.. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Multiple Kasa devices contain an improper authentication vulnerability in the local device-management protocol. An unauthenticated adjacent attacker may send management instructions to an affected device without adequate authentication or authorization, allowing modification of the device state or management settings. Under certain usage conditions involving interaction between the user, mobile application, and device-cloud service, insufficient protection of account-related communications may also expose account information. Successful exploitation may allow an unauthenticated adjacent-network attacker to perform unauthorized device-management actions and disrupt legitimate user control. Under certain conditions, account-related information may also be exposed, potentially leading to compromise of the associated cloud account.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-108473 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-108473?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-108473?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-108473 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • tp-link systems inc.:ep10 v1
  • tp-link systems inc.:ep40 v1
  • tp-link systems inc.:ep40a v1
  • tp-link systems inc.:es20m v1
  • tp-link systems inc.:hs103 v5
  • tp-link systems inc.:hs200 v5
  • tp-link systems inc.:hs210 v3
  • tp-link systems inc.:hs220 v3
  • tp-link systems inc.:hs300 v2
  • tp-link systems inc.:kl110 v4
  • tp-link systems inc.:kl125 v4
  • tp-link systems inc.:kl135 v2
  • tp-link systems inc.:kl420l5 v1
  • tp-link systems inc.:kp115 v1
  • tp-link systems inc.:kp200 v3
  • tp-link systems inc.:kp303 v2
  • tp-link systems inc.:kp400 v3
  • tp-link systems inc.:kp401 v1
  • tp-link systems inc.:kp405 v1
  • tp-link systems inc.:ks200 v1
  • tp-link systems inc.:ks200m v1
  • tp-link systems inc.:ks220 v1
  • tp-link systems inc.:ks220m v1
  • tp-link systems inc.:ks230 kit v2

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. HS103 v5before 1.1.3 Build 250908 Rel.112508
TP-Link Systems Inc. EP10 v1before 1.1.1 Build 250908 Rel.112508
TP-Link Systems Inc. EP40 v1before 1.1.0 Build 250225 Rel.171723
TP-Link Systems Inc. HS200 v5before 1.1.2 Build 241220 Rel.165559
TP-Link Systems Inc. KP401 v1before 1.1.2 Build 241223 Rel.094434
TP-Link Systems Inc. KS230 KIT v2before 1.1.4 Build 241223 Rel.105830
TP-Link Systems Inc. KP405 v1before 1.1.0 Build 250225 Rel.174632
TP-Link Systems Inc. HS220 v3before 1.1.4 Build 241220 Rel.171050
TP-Link Systems Inc. KP115 v1before 1.1.1 Build 250908 Rel.112945
TP-Link Systems Inc. HS210 v3before 1.1.0 Build 250225 Rel.163425
TP-Link Systems Inc. HS300 v2before 1.1.2 Build 241220 Rel.171333
TP-Link Systems Inc. KP200 v3before 1.1.0 Build 250225 Rel.171724
TP-Link Systems Inc. KP303 v2before 1.1.2 Build 241220 Rel.173321
TP-Link Systems Inc. KS200 v1before 1.1.2 Build 241223 Rel.103857
TP-Link Systems Inc. EP40A v1before 1.1.1 Build 250908 Rel.112526
TP-Link Systems Inc. KS220 v1before 1.1.3 Build 241223 Rel.105515
TP-Link Systems Inc. KS200M v1before 1.1.4 Build 241223 Rel.104700
TP-Link Systems Inc. ES20M v1before 1.1.6 Build 250522 Rel.210254
TP-Link Systems Inc. KS220M v1before 1.1.6 Build 250522 Rel.210254
TP-Link Systems Inc. KP400 v3before 1.1.0 Build 250225 Rel.171723
TP-Link Systems Inc. KL125 v4before 1.1.1 Build 260710 Rel.082646
TP-Link Systems Inc. KL135 v2before 1.1.1 Build 260710 Rel.082646
TP-Link Systems Inc. KL110 v4before 1.1.1 Build 260710 Rel.082646
TP-Link Systems Inc. KL420L5 v1before 1.4.2 Build 260605 Rel.035033

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON