# CVE-2026-75618: RTSP Null Pointer Dereference Denial-of-Service Vulnerability on TP-Link Tapo C100 and C101

> A local attacker can crash the RTSP service on TP-Link Tapo cameras, causing a device reboot and temporary denial of video streaming.

- **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:** 19 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-7r3v-6vvc-j8rv

## What is CVE-2026-75618?

CVE-2026-75618 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C100 v5, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tapo C100/C101 V5 contains a null pointer dereference vulnerability in the RTSP service. An attacker on the local network can send specially crafted requests that cause the service to dereference an invalid pointer, resulting in a service crash and device reboot. Successful exploitation can disrupt live video streaming functionality and cause a temporary denial-of-service condition.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 2 products.


Products: Tp-Link Tapo C100 Firmware, Tp-Link Tapo C101 Firmware.

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

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

## Is CVE-2026-75618 being exploited?

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

## Other vulnerabilities in TP-Link Systems Inc. Tapo C100 v5

- [CVE-2026-75619](https://insights.sbomify.com/CVE-2026-75619/): RTSP Heap Buffer Overflow Denial-of-Service Vulnerability on TP-Link Tapo C100 and C101 (medium 6.9)
- [CVE-2023-39610](https://insights.sbomify.com/CVE-2023-39610/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75618 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C100 v5, published on 19 Aug 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-75618 in the wild and no public exploit code.

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

## Sources

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

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