# CVE-2026-105672: Unauthenticated JSON API Authorization Bypass Vulnerability in TP-Link Tapo C325WB

> An unauthenticated adjacent-network attacker can bypass session verification to access live video, modify settings, and obtain sensitive information.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-9544-m82g-43mh

## What is CVE-2026-105672?

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

### Official description

TP-Link Tapo
C325WB V2 contains an unauthenticated authorization bypass vulnerability in the
HTTPS JSON API dispatcher on TCP port 443. An attacker on the adjacent network
can append an onboarding-scoped object to a JSON request to bypass session
verification and invoke privileged actions without authentication. 

Successful
exploitation may allow an unauthenticated adjacent-network attacker to access
live video and audio, modify device settings, and obtain sensitive device
information or secrets.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-105672 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105672 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo C325WB v2, published on 8 Oct 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-105672 in the wild and no public exploit code.

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

## Sources

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

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