# CVE-2026-34123: Whitelist Validation Bypass in TP-Link Tapo C520WS

> Attackers with restricted accounts can bypass API whitelist restrictions to execute unauthorized sensitive operations, causing device resets or configuration changes.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-x7cf-gm5r-xq89

## What is CVE-2026-34123?

CVE-2026-34123 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo C520WS v2, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Tapo
C520WS v2, restricted accounts (for example, hub users) are intended to execute
only a limited set of low‑sensitivity operations. Due to a logic flaw in the
device’s API authorization mechanism, an attacker can craft requests that
leverage legitimate “method mapping” behavior to bypass whitelist restrictions,
allowing restricted operations to be masked as permitted requests and executed.

Successful
exploitation may allow an attacker (with access to a restricted account) to
execute unauthorized sensitive operations. 
Depending on the operation invoked, impact could include device
resets, unintended configuration changes, or disruption of normal operation,
leading to loss of availability and integrity of the device.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-34123 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34123 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo C520WS v2, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34123 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Tapo C520WS v2. 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-34123/ (Markdown: https://insights.sbomify.com/CVE-2026-34123/index.md)
```

## Sources

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

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