Skip to content
Fencer Intel
high 8.8

CVE-2026-3294 json

Authentication Logic Vulnerability on Multiple TP-Link Range Extenders

published 5mo ago modified 3mo ago also EUVD-2026-31502

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

An authentication logic vulnerability in multiple TP-Link range extenders allows an unauthenticated attacker on an adjacent network to manipulate a login parameter and reset the administrator password due to insufficient validation.

Successful exploitation allows an attacker to obtain full administrative control of the affected device, potentially impacting on confidentiality, integrity, and availability.

Patch / fix

  • TP-Link Systems Inc. Archer RE650 v1 V1_20260429
  • TP-Link Systems Inc. Archer RE305 v1 V1_20260515
  • TP Link Systems Inc. Archer RE360 v1 V1_20260515
  • TP-Link Systems Inc. TL-WA860RE v4 V4_20260515
  • TP-Link Systems Inc. RE580D v1 V1_20260515

Is CVE-2026-3294 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 8.7 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
CNA 4.0 8.7 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/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 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • TP-Link Systems Inc. Archer RE650 v1
  • TP-Link Systems Inc. Archer RE305 v1
  • TP Link Systems Inc. Archer RE360 v1
  • TP-Link Systems Inc. TL-WA860RE v4
  • TP-Link Systems Inc. RE580D v1

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.