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.
0.3%(unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th 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: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-109506 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109506?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109506?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-109506 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.:re190 v5
tp-link systems inc.:re200 v5
tp-link systems inc.:re205 v4
tp-link systems inc.:re215 v1
tp-link systems inc.:re220 v3
tp-link systems inc.:re230 v2
tp-link systems inc.:re300 v2
tp-link systems inc.:re305 v4
tp-link systems inc.:re315 v1
tp-link systems inc.:re330 v1
tp-link systems inc.:re335 v1
tp-link systems inc.:re365 v2
tp-link systems inc.:re365 v3
tp-link systems inc.:re450 v4.8
tp-link systems inc.:re550 v1
tp-link systems inc.:re750c v4
Versions
From the CNA's record in the CVE List.
Product
Affected
TP-Link Systems Inc. RE190 v5
before V5_260904
TP-Link Systems Inc. RE200 v5
before V5_260904
TP-Link Systems Inc. RE205 v4
before V4_260904
TP-Link Systems Inc. RE215 v1
before V1_260904
TP-Link Systems Inc. RE220 v3
before V3_260904
TP-Link Systems Inc. RE230 v2
before V2_260904
TP-Link Systems Inc. RE300 v2
before V2_260904
TP-Link Systems Inc. RE305 v4
before V4_260904
TP-Link Systems Inc. RE330 v1
before V1_260904
TP-Link Systems Inc. RE335 v1
before V1_260904
TP-Link Systems Inc. RE365 v2
before V2_260904
TP-Link Systems Inc. RE365 v3
before V3_260904
TP-Link Systems Inc. RE750C v4
before V4_260904
TP-Link Systems Inc. RE450 v4.8
before V4_260915
TP-Link Systems Inc. RE550 v1
before V1_260915
TP-Link Systems Inc. RE315 v1
before V1_260904 rel3959
GitHub PoC
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
lukaspalm/CVE-2026-109506Harbor Check: matches CVE0 stars, Python, created Technical writeup of CVE-2026-109506, a vulnerability I found in multiple TP-Link Wi-Fi Range Extenders
Attack patterns (CAPEC)
CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High