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 109506 improper authentication in multiple tp link wifi
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
Medium · CVSS 5.9CVE-2026-109506

Improper Authentication in Multiple TP-Link WiFi RepeatersCVE-2026-109506

Answer in brief

CVE-2026-109506 records a Medium severity (CVSS 5.9) vulnerability in Improper Authentication in Multiple TP-Link WiFi Repeaters. The current sources do not mark it as known exploited. The current feed maps TP-Link Systems Inc./RE190 v5 (generic), TP-Link Systems Inc./RE200 v5 (generic), TP-Link Systems Inc./RE205 v4 (generic), TP-Link Systems Inc./RE215 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
Medium · CVSS 5.9
Exploitation
Not marked as known exploited
Affected software
16 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.9. 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./RE190 v5 (generic), TP-Link Systems Inc./RE200 v5 (generic), TP-Link Systems Inc./RE205 v4 (generic), TP-Link Systems Inc./RE215 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./RE190 v5generic>=0 <V5_260904V5_260904
TP-Link Systems Inc./RE200 v5generic>=0 <V5_260904V5_260904
TP-Link Systems Inc./RE205 v4generic>=0 <V4_260904V4_260904
TP-Link Systems Inc./RE215 v1generic>=0 <V1_260904V1_260904
TP-Link Systems Inc./RE220 v3generic>=0 <V3_260904V3_260904
TP-Link Systems Inc./RE230 v2generic>=0 <V2_260904V2_260904
TP-Link Systems Inc./RE300 v2generic>=0 <V2_260904V2_260904
TP-Link Systems Inc./RE305 v4generic>=0 <V4_260904V4_260904
TP-Link Systems Inc./RE315 v1generic>=0 <V1_260904 rel3959V1_260904 rel3959, V1_260904
TP-Link Systems Inc./RE330 v1generic>=0 <V1_260904V1_260904
TP-Link Systems Inc./RE335 v1generic>=0 <V1_260904V1_260904
TP-Link Systems Inc./RE365 v2generic>=0 <V2_260904V2_260904
TP-Link Systems Inc./RE365 v3generic>=0 <V3_260904V3_260904
TP-Link Systems Inc./RE450 v4.8generic>=0 <V4_260915V4_260915
TP-Link Systems Inc./RE550 v1generic>=0 <V1_260915V1_260915
TP-Link Systems Inc./RE750C v4generic>=0 <V4_260904V4_260904

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for TP-Link Systems Inc./RE190 v5, TP-Link Systems Inc./RE200 v5, TP-Link Systems Inc./RE205 v4.
  2. 2Review the reported fix. Update TP-Link Systems Inc./RE190 v5 to V5_260904; TP-Link Systems Inc./RE200 v5 to V5_260904; TP-Link Systems Inc./RE205 v4 to V4_260904; TP-Link Systems Inc./RE215 v1 to V1_260904; TP-Link Systems Inc./RE220 v3 to V3_260904; TP-Link Systems Inc./RE230 v2 to V2_260904; TP-Link Systems Inc./RE300 v2 to V2_260904; TP-Link Systems Inc./RE305 v4 to V4_260904; TP-Link Systems Inc./RE315 v1 to V1_260904 rel3959; TP-Link Systems Inc./RE330 v1 to V1_260904; TP-Link Systems Inc./RE335 v1 to V1_260904; TP-Link Systems Inc./RE365 v2 to V2_260904; TP-Link Systems Inc./RE365 v3 to V3_260904; TP-Link Systems Inc./RE450 v4.8 to V4_260915; TP-Link Systems Inc./RE550 v1 to V1_260915; TP-Link Systems Inc./RE750C v4 to V4_260904 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 TP-Link Wi-Fi range extenders use a custom, reversible XOR-and-dictionary transformation in the HTTP web-management login flow. An unauthenticated attacker on the same local network who can capture the network traffic associated with legitimate administrator login may be able to derive an alternative credential value that produces the same accepted authentication result and use it to authenticate to the device’s web-management interface with administrator privileges. Exploitation requires the management login to use HTTP and the attacker to observe the session key, dictionary, and login value associated with a legitimate administrator login. Successful exploitation may allow an unauthenticated adjacent attacker to gain administrator access to the affected device and modify exposed configuration settings.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Sentry: Improper authentication on SAML SSO process allows user identity linkingAlso CWE-287
  • cemtan sar2html sar2html.py deleteAll missing authenticationAlso CWE-287
  • PAN-OS: Denial of Service (DoS) Vulnerabilities in Network ServicesSame generic ecosystem
  • BentoPDF: SSRF via DNS Rebinding (TOCTOU) in Cloudflare CORS Proxy WorkerSame generic ecosystem
  • CRLF header injection in vertx-mail-client allows manipulation of outgoing SMTP messagesSame generic ecosystem
  • DataEase Datasource/Dataset Folder Name Stored Cross-Site ScriptingSame generic ecosystem

Record context

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