dbcve.org
Tapo C110 FirmwareOperating system · Tp Link

CVE-2026-6250

HIGH · 8.1 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 1.5.4 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authenticated format string vulnerability in the ONVIF service of Tapo C110 v2 allows an authenticated attacker to manipulate stack memory through user-controlled input being interpreted as a format string. This enables control flow hijacking via return address manipulation to trigger unauthorized factory resets, resulting in credential deletion and service disruption.

MitigationApply vendor firmware patches when available; until then, restrict ONVIF service access to trusted networks or disable if unused, and rotate credentials to limit authenticated attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tapo C110 FirmwareOperating system
Affected:< 1.5.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the Tapo mobile app or web interface and navigate to the device settings or firmware information section to view the current firmware version
    Affected if The firmware version displayed is less than 1.5.4 (for example, 1.5.3, 1.5.2, or earlier)
  2. Confirm ONVIF service is enabled
    Check the device settings in the Tapo app or web interface for ONVIF configuration options, or scan the device network ports (typically 2020 or 8080 for ONVIF) to confirm the service is listening
    Affected if The ONVIF service is enabled and accessible on the device
  3. Verify ONVIF service network exposure
    Use a network scanner or check router firewall settings to determine if ONVIF ports are exposed to untrusted networks or the internet
    Affected if The ONVIF service is reachable from untrusted networks or directly from the internet
  4. Review ONVIF authentication credentials
    Check the ONVIF user credentials configured in the device settings or examine access logs for ONVIF authentication attempts
    Affected if Simple, default, or easily guessable ONVIF credentials are in use, or credentials are shared across multiple devices

The device is affected if it is a Tapo C110 with firmware version below 1.5.4 and has the ONVIF service enabled and accessible, especially from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.4 or later
Fixed in 1.5.4
Interim mitigation

Apply vendor firmware patches when available; until then, restrict ONVIF service access to trusted networks or disable if unused, and rotate credentials to limit authenticated attack surface.

Recommended fix High confidence

Tapo C110 Firmware 1.5.4

  1. Locate the Tapo C110 device in your network or access it via the Tapo app
  2. Navigate to the device settings and check the current firmware version
  3. Download firmware version 1.5.4 or later from the official TP-Link support page (www.tp-link.com)
  4. Follow TP-Link's official firmware update instructions to apply the update to the Tapo C110 device
  5. After updating, verify the firmware version shows 1.5.4 or higher
  6. Confirm the ONVIF service is functioning normally post-update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapo C110 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data