cve.bz

CVE-2026-105810 tp-link systems inc. tapo c320ws v2: Stack-based Buffer Overflow

8.5 highEPSS 0.5%

High (8.5) in tp-link systems inc. tapo c320ws v2. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105810 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105810?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105810?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105810 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • tp-link systems inc.:tapo c320ws v2

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Tapo C320WS v2before 1.6.6 Build 260917 Rel.81089n

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • M0ud4/CVE-2026-105810 Harbor Check: matches CVE 3 stars, Python, created
    CVE-2026-105810 TP-Link Tapo C320WS authenticated connectAp stack overflow (RCE as root)

References

Check your stackJSON