Skip to main content

Tapo C320WS CVE-2026-105810

| EUVDEUVD-2026-104523 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-19 TPLink GHSA-xj9v-v8cr-7969
8.5
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain authenticated adjacent-network access
  2. Delivery
    Craft oversized encrypted password field
  3. Exploit
    Submit to onboarding Wi-Fi config path
  4. Execution
    Overflow stack buffer (CWE-121)
  5. Persist
    Execute commands as root
  6. Impact
    Seize camera control and disrupt availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to (1) be on the adjacent network segment used for the camera's local onboarding (AV:A - not routable internet access), and (2) hold valid authentication to the device (PR:H). The specific trigger is the local onboarding Wi-Fi configuration path: the attacker must reach that onboarding/provisioning endpoint and supply a crafted request with an oversized encrypted password field that overflows the stack buffer. Limiting factors that reduce real-world risk: the device must be reachable on the local/adjacent network (typical home or provisioning LAN, not WAN), the attacker must already be authenticated, and only the Tapo C320WS V2.0 hardware/firmware is affected. No user interaction is required (UI:N), and successful exploitation yields root, so an already-authenticated adjacent attacker faces low complexity (AC:L).

Impact

This is a genuine but conditionally-gated issue rather than a drop-everything emergency. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:H/UI:N, score 8.5) tells a consistent story with the description: exploitation requires adjacent-network access (not internet-facing remote) and high privileges (PR:H), meaning the attacker must already be authenticated to the camera's local onboarding interface. The high VC/VI/VA impacts (root command execution) justify the High severity, but the two preconditions - physical/network adjacency plus valid authentication - materially reduce real-world exploitability versus a true unauthenticated remote RCE. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis; the absence of KEV combined with the authenticated/adjacent constraints suggests this is not a candidate for widespread automated exploitation. No SSVC decision data was supplied. The principal signals (CVSS vector and description) are mutually consistent - both point to authenticated adjacent access - so there is no major conflict to flag, though the practical bar (already-authenticated adjacent attacker) means the residual risk is dominated by insider, shared-network, or post-compromise scenarios rather than mass exploitation.

Exploit ScenarioDerived

An attacker already authenticated to a Tapo C320WS V2.0 camera and present on the same adjacent network (e.g. the local Wi-Fi or onboarding segment) submits a crafted onboarding request carrying an oversized encrypted password field. The oversized field overflows a stack buffer in the Wi-Fi configuration handler, overwriting stack state and yielding arbitrary command execution as root. No public exploit code was identified at time of analysis, and the attack requires valid credentials plus network adjacency (CVSS AV:A/PR:H).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

Authenticated stack-based buffer overflow in TP-Link Tapo C320WS V2.0 cameras lets an attacker on the adjacent network who already holds valid device credentials overwrite stack memory through an oversized encrypted password field submitted to the local onboarding Wi-Fi configuration path, ultimately executing commands as root. Because the trigger lives in the provisioning endpoint that is only reachable on the local or onboarding LAN (not from the internet) and requires high-privilege authentication, exploitation is conditionally gated rather than broadly opportunistic; no public exploit code or confirmed active exploitation was identified at time of analysis. Successful abuse lets the attacker take control of the camera, alter its behavior, read sensitive local configuration, and disrupt availability, and TP-Link has published fixed firmware on its download portal.

RemediationAI

Vendor-released firmware addressing this overflow is available: Patch available per vendor advisory - download and flash the latest Tapo C320WS V2 firmware from https://www.tp-link.com/en/support/download/tapo-c320ws/v2/#Firmware-Release-Notes (or the US mirror at https://www.tp-link.com/us/support/download/tapo-c320ws/#Firmware-Release-Notes) and confirm the installed build against the release notes, using https://www.tp-link.com/us/support/faq/5351/ for the vendor's own guidance. Because the input data does not name an exact fixed version string, verify the version on the download page rather than relying on a number quoted elsewhere, and apply the update through the Tapo app or the camera's local management interface, not over an untrusted network. Until every V2 unit is patched, compensating controls with real trade-offs apply: keep the camera on an isolated IoT VLAN or dedicated SSID so the adjacent-network onboarding path (AV:A) is not shared with laptops, phones, and guests - this blunts the attack precondition but also breaks any app or integration that expects flat-LAN discovery; complete onboarding and Wi-Fi provisioning on a trusted segment and then remove or firewall access to the provisioning endpoint afterwards, accepting that re-provisioning will require temporarily restoring that access; enforce strong, unique camera credentials and rotate any shared accounts, since PR:H means a valid login is a prerequisite, though this only raises the bar and does not fix the overflow; and disable cloud/remote access features you do not use to reduce exposure surface, at the cost of losing remote viewing. Monitor the camera for unexpected reboots, configuration changes, or dropped streams, which can indicate a crashed or hijacked process.

Affected VersionsENISA

Tapo C320WS v2 0 <1.6.6 Build 260917 Rel.81089n

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-121 stack-based buffer overflow in the firmware's local onboarding/provisioning component. During Wi-Fi configuration the device accepts a request carrying an encrypted password field and copies it into a fixed-size stack buffer without validating the length; an oversized value spills past the buffer boundary and overwrites adjacent stack state, including saved control data, which under the device's runtime privileges translates into root-level command execution. The assessed vector CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (matching the vendor's CVSS:4.0 AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H rating of 8.5) makes the exposure geometry clear: AV:A confines reachability to the adjacent/broadcast segment where onboarding traffic flows, PR:H requires an already-authenticated principal, UI:N means no victim action is needed, and AC:L reflects that once those two preconditions are met the overflow itself is straightforward to trigger. The CPE cpe:2.3:a:tp-link_systems_inc.:tapo_c320ws_v2:*:*:*:*:*:*:*:* scopes the issue to the V2 hardware revision's firmware line; V1 and other Tapo models are not described by this identifier. In practice the bug class matters because the provisioning path handles pre-shared or encrypted credentials before the camera joins a network, so any hardening mistake there sits directly beneath the device's highest privilege level.

Know when Tapo C320Ws V2 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TPLink) PRIMARY 8.5 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

Adjacent onboarding network gives AV:A; authenticated attacker gives PR:H; no interaction needed (UI:N); root command execution on the single device yields C:H/I:H/A:H with no scope change (S:U).

3.1 AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Tapo C320WS V2.0 contains an authenticated stack-based buffer overflow in the local onboarding Wi-Fi configuration path. An authenticated attacker on the adjacent network can submit a crafted request containing an oversized encrypted password field, overwrite stack state, and execute commands with root privileges.

Successful exploitation may allow an authenticated adjacent-network attacker to take control of the affected camera, modify camera behavior, access sensitive local configuration, and disrupt device availability.

Executive ViewAI

Why It Matters

TP-Link Tapo C320WS V2.0 surveillance cameras carry a high-severity firmware flaw that lets someone who already holds valid device credentials, and who is connected to the same local network segment, take full root-level control of the camera. Reachability is confined to local and onboarding networks rather than the internet, and no public exploit identified at time of analysis, so practical risk concentrates on sites where these cameras share a LAN with other devices, guests, or contractors. Leadership should care because a successful compromise hands over a physical security sensor - allowing behavior changes, disclosure of local configuration, and disruption of surveillance at the affected site.

Business Impact: Medium
Compensating Controls

Apply vendor patch. Until firmware is deployed, isolate cameras on a dedicated IoT VLAN with no adjacent untrusted hosts, restrict access to the onboarding/provisioning interface, rotate device credentials, and monitor camera behavior and configuration changes for anomalies.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
popular TP-Link consumer security camera, but a specific model/version
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy