CyberSecBulletin
CVE-2026-3294NVD status: Analyzed

Archer RE650 v1: Missing Authorization

Published Updated By the CyberSecBulletin desk

CVE-2026-3294 is a high-severity missing authorization vulnerability in Archer RE650 v1 from TP-Link, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version V1_20260429 as the first without the flaw, so updating Archer RE650 v1 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Archer RE650 v1 to V1_20260429 or a later version.
  2. Update Archer RE305 v1 to V1_20260515 or a later version.
  3. Update Archer RE360 v1 to V1_20260515 or a later version.
  4. Read the advisory on tp-link.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
TP-LinkArcher RE650 v1before V1_20260429V1_20260429
TP-LinkArcher RE305 v1before V1_20260515V1_20260515
TP-LinkArcher RE360 v1before V1_20260515V1_20260515
TP-LinkTL-WA860RE v4before V4_20260515V4_20260515
TP-LinkRE580D v1before V1_20260515V1_20260515
TP-LinkRe305 Firmwarebefore 2026051520260515
TP-LinkRe360 Firmwarebefore 2026051520260515
TP-LinkRe580d Firmwarebefore 2026051520260515
TP-LinkRe650 Firmwarebefore 2026042920260429
TP-LinkTl-wa860re Firmwarebefore 2026051520260515

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.7HighCNA
CVSS 3.18.8HighNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.