Read the docs
TI-2026-81495 Aliases CVE-2026-102816GHSA-7gfj-r5h8-6w5v

Unauthenticated wireless regulatory region change in TP-Link RE305

Priority LOW 23CWE-306Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-306.

Summary

TP-Link RE305 V3 devices before 1.1.8 Build 20260921 Rel. 42853 have a missing authorization check in the country or region configuration interface, tracked as CWE-306. An unauthenticated attacker on the same local network can change the wireless regulatory region and force the device to reapply its wireless configuration. Successful exploitation can interrupt wireless connections, make channels unavailable, disconnect clients, or apply parameters meant for a different regulatory region.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

An authorization vulnerability exists in the country or region configuration interface of TP-Link RE305 V3. An unauthenticated attacker on the same local network may modify the wireless regulatory region and force the device to reapply its wireless configuration.  Successful exploitation may cause wireless connection interruptions, unavailable channels, client disconnections, or wireless service instability, and may cause the device to apply parameters intended for a different regulatory region.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00168 6th percentileScored 2026-11-07
Fix Fixed RE305 v3 (TP-Link Systems Inc.): 1.1.8 Build 20260921 Rel. 42853

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
TP-LinkRE305 v3before 1.1.8 Build 20260921 Rel. 428531.1.8 Build 20260921 Rel. 42853Patch availableCNA
  • RE305 v3 VendorTP-Link Affected before 1.1.8 Build 20260921 Rel. 42853 Fixed in 1.1.8 Build 20260921 Rel. 42853 Patch available CNA

Remediation

Update TP-Link RE305 v3 to 1.1.8 Build 20260921 Rel. 42853 or later.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA RE305 v3 (TP-Link Systems Inc.) Fixed in 1.1.8 Build 20260921 Rel. 42853

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    TP-Link Systems RE305 v3 1.1.8 Build 20260921 Rel. 42853

    5 records Highest priority Priority MEDIUM 1 MEDIUM, 4 LOW

    Other records, highest priority first

    • TI-2026-81493 Authentication weakness in TP-Link RE305 TDDP v2 allows root command executionPriority MEDIUM 40
    • TI-2026-81494 Command injection in TP-Link RE305 tmpServer grants root accessPriority LOW 33
    • TI-2026-81491 Hard-coded AES key in TP-Link RE305 and Archer C7 backup encryptionPriority LOW 29
    Show all 5 records →

Timeline

  1. 2026-10-27 Threatist record created from CVE-2026-102816
  2. 2026-10-27 Alias added: GHSA-7gfj-r5h8-6w5v
  3. 2026-11-04 CISA SSVC decision points changed

References

Patch 2

Advisory 1

  • TI-2023-16571 TP-Link TL-WR940N V2/V4, TL-WR841N V8/V10, and TL-WR740N V1/V2 was discovered to contain… KEVCVSS 3.1HIGH 8.8
  • TI-2023-01313 Command injection in TP-Link Archer AX21 KEVCVSS 3.1HIGH 8.8
  • TI-2020-14907 TP-Link TL-WA855RE V5 20200415-rel37464 devices allow an unauthenticated attacker (on the… KEVCVSS 3.1HIGH 8.8
  • TI-2025-08589 Authenticated RCE via Parental Control command injection KEVCVSS 4.0HIGH 8.6
  • TI-2015-02672 Directory traversal vulnerability in TP-LINK Archer C5 (1.2) with firmware before 150317… KEVCVSS 3.1HIGH 7.5
  • TI-2023-27456 Authentication bypass by spoofing in TP-Link TL-WR841N KEVCVSS 3.1MEDIUM 6.5
See all 636 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences