# CVE-2026-102816: Unauthenticated Wireless Regulatory Region Configuration in TP-Link RE305


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-7gfj-r5h8-6w5v

## What is CVE-2026-102816?

CVE-2026-102816 is a medium-severity vulnerability in TP-Link Systems Inc. RE305 v3, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-102816?


## How do I fix CVE-2026-102816?

No fix has been published for CVE-2026-102816 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102816 being exploited?

There is no known exploitation of CVE-2026-102816 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102816 and fix it if it is affected.

What it is: CVE-2026-102816 is a medium-severity vulnerability in TP-Link Systems Inc. RE305 v3, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102816 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. RE305 v3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102816/ (Markdown: https://insights.sbomify.com/CVE-2026-102816/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102816
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102816
- OSV: https://osv.dev/vulnerability/CVE-2026-102816

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102816/
Summaries are generated and may contain mistakes; the official description above is the record.