# CVE-2026-104945: Authenticated ONVIF PTZ Out-of-Bounds Stack Write Denial of Service in TP-Link Tapo C500

> An authenticated attacker can cause a denial of service in TP-Link Tapo C500 cameras by triggering an out-of-bounds stack write via ONVIF PTZ handlers.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-879v-46j6-mx37

## What is CVE-2026-104945?

CVE-2026-104945 is a medium-severity memory corruption vulnerability in TP-Link Systems Inc. Tapo C500 v2.0, published on 6 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
C500 v2.0 contains an out-of-bounds stack write vulnerability in its ONVIF PTZ
SOAP handlers. An authenticated ONVIF client can submit an excessive number of
preset-related elements, causing writes beyond the bounds of fixed-size stack
arrays and resulting in a crash of the affected service.

Successful
exploitation may allow an authenticated attacker to cause the affected service
to crash, resulting in a denial-of-service condition. Repeated exploitation may
repeatedly disrupt camera management and PTZ-related functionality until the
service recovers or restarts.

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

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


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

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

## Is CVE-2026-104945 being exploited?

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

Public exploit code:

- https://github.com/anaskalt/CVE-2026-104945 (github_poc): https://github.com/anaskalt/CVE-2026-104945

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104945 is a medium-severity memory corruption vulnerability in TP-Link Systems Inc. Tapo C500 v2.0, published on 6 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-104945 in the wild and no public exploit code.

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

## Sources

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

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