# CVE-2026-6250: Authenticated Format String Injection on TP-Link Tapo C110

> Authenticated attackers can exploit a format string vulnerability in the ONVIF service to trigger unauthorized factory resets and service disruption.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/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:** 11 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-4gmj-9m2m-6h5f

## What is CVE-2026-6250?

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

### Official description

An
authenticated format string vulnerability exists in the ONVIF service of Tapo
C110 v2 due to improper handling of user-controlled input.  Externally controlled data is interpreted as
a format string, which can be used to manipulate stack memory, including
control flow data such as return addresses.

A remote
authenticated attacker may redirect execution flow to existing internal
functions, triggering an unauthorized factory reset, leading to loss of
configuration, deletion of stored credentials and service disruption.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Tp-Link Tapo C110 Firmware.

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

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

## Is CVE-2026-6250 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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