# CVE-2026-105673: Unauthenticated RTSP Tunnel Denial-of-Service Vulnerability in TP-Link Tapo C325WB

> An unauthenticated attacker can crash the RTSP streaming daemon via crafted requests, disrupting video services on TP-Link Tapo C325WB cameras.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 9 Oct 2026
- **Also known as:** GHSA-mjqg-3r8q-j4cx

## What is CVE-2026-105673?

CVE-2026-105673 is a high-severity memory corruption 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

An
unauthenticated denial-of-service vulnerability exists in Tapo C325WB v2 in the
RTSP streaming service on TCP port 554 when the Camera Account feature is
enabled. A crafted pair of RTSP-over-HTTP tunneling requests can cause memory
corruption and crash the streaming daemon. 

Successful
exploitation may allow an unauthenticated adjacent-network attacker to disrupt
live video and related streaming functions until the affected service recovers
or restarts.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-105673 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105673 is a high-severity memory corruption 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-105673 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-105673/ (Markdown: https://insights.sbomify.com/CVE-2026-105673/index.md)
```

## Sources

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

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