HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 108473 improper authentication and credential exposure
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High ยท CVSS 8.7CVE-2026-108473

Improper Authentication and Credential Exposure in Multiple TP-Link Kasa DevicesCVE-2026-108473

Answer in brief

CVE-2026-108473 records a High severity (CVSS 8.7) vulnerability in Improper Authentication and Credential Exposure in Multiple TP-Link Kasa Devices. The current sources do not mark it as known exploited. The current feed maps TP-Link Systems Inc./EP10 v1 (generic), TP-Link Systems Inc./EP40A v1 (generic), TP-Link Systems Inc./EP40 v1 (generic), TP-Link Systems Inc./ES20M v1 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 14, 2026Updated Oct 14, 2026Source checked Oct 14, 2026First seen by HOL Oct 14, 2026Material review Oct 14, 2026
Upstream Advisory

Key facts

Risk
High ยท CVSS 8.7
Exploitation
Not marked as known exploited
Affected software
24 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps TP-Link Systems Inc./EP10 v1 (generic), TP-Link Systems Inc./EP40A v1 (generic), TP-Link Systems Inc./EP40 v1 (generic), TP-Link Systems Inc./ES20M v1 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
TP-Link Systems Inc./EP10 v1generic>=0 <1.1.1 Build 250908 Rel.1125081.1.1 Build 250908 Rel.112508, 1.1.1
TP-Link Systems Inc./EP40A v1generic>=0 <1.1.1 Build 250908 Rel.1125261.1.1 Build 250908 Rel.112526, 1.1.1
TP-Link Systems Inc./EP40 v1generic>=0 <1.1.0 Build 250225 Rel.1717231.1.0 Build 250225 Rel.171723, 1.1.0
TP-Link Systems Inc./ES20M v1generic>=0 <1.1.6 Build 250522 Rel.2102541.1.6 Build 250522 Rel.210254, 1.1.6
TP-Link Systems Inc./HS103 v5generic>=0 <1.1.3 Build 250908 Rel.1125081.1.3 Build 250908 Rel.112508, 1.1.3
TP-Link Systems Inc./HS200 v5generic>=0 <1.1.2 Build 241220 Rel.1655591.1.2 Build 241220 Rel.165559, 1.1.2
TP-Link Systems Inc./HS210 v3generic>=0 <1.1.0 Build 250225 Rel.1634251.1.0 Build 250225 Rel.163425, 1.1.0
TP-Link Systems Inc./HS220 v3generic>=0 <1.1.4 Build 241220 Rel.1710501.1.4 Build 241220 Rel.171050, 1.1.4
TP-Link Systems Inc./HS300 v2generic>=0 <1.1.2 Build 241220 Rel.1713331.1.2 Build 241220 Rel.171333, 1.1.2
TP-Link Systems Inc./KL110 v4generic>=0 <1.1.1 Build 260710 Rel.0826461.1.1 Build 260710 Rel.082646, 1.1.1
TP-Link Systems Inc./KL125 v4generic>=0 <1.1.1 Build 260710 Rel.0826461.1.1 Build 260710 Rel.082646, 1.1.1
TP-Link Systems Inc./KL135 v2generic>=0 <1.1.1 Build 260710 Rel.0826461.1.1 Build 260710 Rel.082646, 1.1.1
TP-Link Systems Inc./KL420L5 v1generic>=0 <1.4.2 Build 260605 Rel.0350331.4.2 Build 260605 Rel.035033, 1.4.2
TP-Link Systems Inc./KP115 v1generic>=0 <1.1.1 Build 250908 Rel.1129451.1.1 Build 250908 Rel.112945, 1.1.1
TP-Link Systems Inc./KP200 v3generic>=0 <1.1.0 Build 250225 Rel.1717241.1.0 Build 250225 Rel.171724, 1.1.0
TP-Link Systems Inc./KP303 v2generic>=0 <1.1.2 Build 241220 Rel.1733211.1.2 Build 241220 Rel.173321, 1.1.2
TP-Link Systems Inc./KP400 v3generic>=0 <1.1.0 Build 250225 Rel.1717231.1.0 Build 250225 Rel.171723, 1.1.0
TP-Link Systems Inc./KP401 v1generic>=0 <1.1.2 Build 241223 Rel.0944341.1.2 Build 241223 Rel.094434, 1.1.2
TP-Link Systems Inc./KP405 v1generic>=0 <1.1.0 Build 250225 Rel.1746321.1.0 Build 250225 Rel.174632, 1.1.0
TP-Link Systems Inc./KS200M v1generic>=0 <1.1.4 Build 241223 Rel.1047001.1.4 Build 241223 Rel.104700, 1.1.4
TP-Link Systems Inc./KS200 v1generic>=0 <1.1.2 Build 241223 Rel.1038571.1.2 Build 241223 Rel.103857, 1.1.2
TP-Link Systems Inc./KS220M v1generic>=0 <1.1.6 Build 250522 Rel.2102541.1.6 Build 250522 Rel.210254, 1.1.6
TP-Link Systems Inc./KS220 v1generic>=0 <1.1.3 Build 241223 Rel.1055151.1.3 Build 241223 Rel.105515, 1.1.3
TP-Link Systems Inc./KS230 KIT v2generic>=0 <1.1.4 Build 241223 Rel.1058301.1.4 Build 241223 Rel.105830, 1.1.4

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for TP-Link Systems Inc./EP10 v1, TP-Link Systems Inc./EP40A v1, TP-Link Systems Inc./EP40 v1.
  2. 2Review the reported fix. Update TP-Link Systems Inc./EP10 v1 to 1.1.1 Build 250908 Rel.112508; TP-Link Systems Inc./EP40A v1 to 1.1.1 Build 250908 Rel.112526; TP-Link Systems Inc./EP40 v1 to 1.1.0 Build 250225 Rel.171723; TP-Link Systems Inc./ES20M v1 to 1.1.6 Build 250522 Rel.210254; TP-Link Systems Inc./HS103 v5 to 1.1.3 Build 250908 Rel.112508; TP-Link Systems Inc./HS200 v5 to 1.1.2 Build 241220 Rel.165559; TP-Link Systems Inc./HS210 v3 to 1.1.0 Build 250225 Rel.163425; TP-Link Systems Inc./HS220 v3 to 1.1.4 Build 241220 Rel.171050; TP-Link Systems Inc./HS300 v2 to 1.1.2 Build 241220 Rel.171333; TP-Link Systems Inc./KL110 v4 to 1.1.1 Build 260710 Rel.082646; TP-Link Systems Inc./KL125 v4 to 1.1.1 Build 260710 Rel.082646; TP-Link Systems Inc./KL135 v2 to 1.1.1 Build 260710 Rel.082646; TP-Link Systems Inc./KL420L5 v1 to 1.4.2 Build 260605 Rel.035033; TP-Link Systems Inc./KP115 v1 to 1.1.1 Build 250908 Rel.112945; TP-Link Systems Inc./KP200 v3 to 1.1.0 Build 250225 Rel.171724; TP-Link Systems Inc./KP303 v2 to 1.1.2 Build 241220 Rel.173321; TP-Link Systems Inc./KP400 v3 to 1.1.0 Build 250225 Rel.171723; TP-Link Systems Inc./KP401 v1 to 1.1.2 Build 241223 Rel.094434; TP-Link Systems Inc./KP405 v1 to 1.1.0 Build 250225 Rel.174632; TP-Link Systems Inc./KS200M v1 to 1.1.4 Build 241223 Rel.104700; TP-Link Systems Inc./KS200 v1 to 1.1.2 Build 241223 Rel.103857; TP-Link Systems Inc./KS220M v1 to 1.1.6 Build 250522 Rel.210254; TP-Link Systems Inc./KS220 v1 to 1.1.3 Build 241223 Rel.105515; TP-Link Systems Inc./KS230 KIT v2 to 1.1.4 Build 241223 Rel.105830 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 14, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 14, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Oct 14, 2026

Sources and claim methodology

  • Source referencetp-link.com
  • Source referencetp-link.com
  • Source referencetp-link.com
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • CAI Content Credentials | Improper Input Validation (CWE-20)Same generic ecosystem
  • CAI Content Credentials | Improper Access Control (CWE-284)Same generic ecosystem
  • CAI Content Credentials | Improper Access Control (CWE-284)Same generic ecosystem
  • CAI Content Credentials | Improper Certificate Validation (CWE-295)Same generic ecosystem
  • CAI Content Credentials | Improper Input Validation (CWE-20)Same generic ecosystem
  • CAI Content Credentials | Improper Certificate Validation (CWE-295)Same generic ecosystem

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-306
Source
CVE List V5
Source checked
Oct 14, 2026
References
3 linked sources
Open source record