CVE.org (no NVD analysis yet)· CNA TPLink

CVE-2026-109506: Improper Authentication in Multiple TP-Link WiFi Repeaters

MediumCVSS 5.9 · v4.0—Proof of concept No fix recorded

Noroxi assessment

Priority: Monitor (action score 23/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
Someone on the same network segment can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

EUVD-2026-101602

Published: Oct 14, 2026
Updated: Oct 15, 2026
EPSS: 0.3% · 28th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · TPLink: 5.9; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TPLink). Independent of NVD's CPE analysis and usually ahead of it.

TP-Link Systems Inc. RE190 v5
- before V5_260904affected
TP-Link Systems Inc. RE200 v5
- before V5_260904affected
TP-Link Systems Inc. RE205 v4
- before V4_260904affected
TP-Link Systems Inc. RE215 v1
- before V1_260904affected
TP-Link Systems Inc. RE220 v3
- before V3_260904affected
TP-Link Systems Inc. RE230 v2
- before V2_260904affected
TP-Link Systems Inc. RE300 v2
- before V2_260904affected
TP-Link Systems Inc. RE305 v4
- before V4_260904affected
TP-Link Systems Inc. RE315 v1
- before V1_260904 rel3959affected
TP-Link Systems Inc. RE330 v1
- before V1_260904affected
TP-Link Systems Inc. RE335 v1
- before V1_260904affected
TP-Link Systems Inc. RE365 v2
- before V2_260904affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-10-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

First PoCOct 14, 2026-1 d
PublishedOct 14, 2026
TodayNov 13, 2026+30 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Lukas Palmfinder

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1336 · Oct 15, 2026(TP-Link Çoklu Ürün Güvenlik Bildirimi)

All national notices →

Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Adjacent
Attack complexity: High
Privileges required: None
User interaction: P
Scope: X

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

SSVC exploitation— → noneOct 15, 2026, 9:07 PM UTC
Exploit maturitynone → pocOct 15, 2026, 3:32 AM UTC
Exploit maturity— → noneOct 14, 2026, 8:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.tp-link.com/en/support/download/

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records