dbcve.org
Tapo C200 FirmwareOperating system · Tp Link

CVE-2025-8065

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges 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
A stack-based buffer overflow vulnerability was identified in the ONVIF SOAP XML Parser in Tapo C200 v3 and C520WS v2.6. When processing XML tags with namespace prefixes, the parser fails to validate the prefix length before copying it to a fixed-size stack buffer. It allowed a crafted SOAP request with an oversized namespace prefix to cause memory corruption in stack. An unauthenticated attacker on the same local network may exploit this flaw to enable remote code execution with elevated privileges, leading to full compromise of the device.

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 · high confidence

Stack-based buffer overflow in the ONVIF SOAP XML parser in Tapo C200 v3 and C520WS v2.6. When processing XML tags with namespace prefixes, the parser does not validate prefix length before copying to a fixed-size stack buffer, allowing memory corruption and potential remote code execution by unauthenticated attackers on the same local network.

MitigationIsolate affected devices on a restricted network segment and monitor for vendor firmware updates to address the missing input validation in the XML parser.

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 C200 FirmwareOperating system
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.3.7= 1.3.9= 1.3.11= 1.3.13= 1.3.14= 1.3.15= 1.4.1= 1.4.2= 1.4.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
    Check the physical device label or access the device web interface to confirm the model is Tapo C200 or C520WS
    Affected if Device is Tapo C200 or C520WS
  2. Check firmware version
    Access the device settings page or use the Tapo app to view the firmware version. Compare against affected versions: 1.3.3, 1.3.4, 1.3.5, 1.3.7, 1.3.9, 1.3.11, 1.3.13, 1.3.14, 1.3.15, 1.4.1, 1.4.2, 1.4.4 for C200, or 2.6 for C520WS
    Affected if Firmware version matches one of the listed affected versions
  3. Verify ONVIF service is enabled
    Access the device web interface and check if ONVIF protocol support is enabled in the settings, or use an ONVIF discovery tool to probe the device
    Affected if ONVIF service is active and accessible on the network
  4. Assess network accessibility
    Review network configuration to determine if the device is reachable from untrusted network segments. An attacker on the same local network can send malicious SOAP/XML requests
    Affected if The device is accessible from network segments with untrusted users

If the device is a Tapo C200 or C520WS with an affected firmware version and ONVIF is enabled and accessible on the network, the environment is affected by CVE-2025-8065

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate affected devices on a restricted network segment and monitor for vendor firmware updates to address the missing input validation in the XML parser.

Recommended fix Moderate confidence

Any firmware version newer than 1.3.7 that includes the security fix for CVE-2025-8065 (contact TP-Link support for specific fixed version)

  1. Check TP-Link's official support page (www.tp-link.com) for the Tapo C200 firmware downloads
  2. Look for firmware versions newer than 1.3.7 that address security vulnerabilities
  3. Download and install the latest available firmware version for Tapo C200
  4. After upgrading, verify the device is functioning normally
  5. Confirm the new firmware version is no longer affected by checking the release notes or security advisory

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

Fix this in Tapo C200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8065 — 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-2025-8065 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