Skip to main content
VulnerabilityPublished

CVE-2026-104945: TP-Link Systems Tapo C500 v2.0 · Stack-based Buffer Overflow

Affects TP-Link Systems Tapo C500 v2.0Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.3.5 Build 260810 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.5 Build 260810
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade TP-Link Systems Tapo C500 v2.0 to 1.3.5 Build 260810.

Affected software

ProductAffectedFixed in
TP-Link Systems Inc.Tapo C500 v2.0Affected
  • =0
Fixed in
  • 1.3.5 Build 260810

AI-suggested

If you cannot patch yet, restrict access to authenticated ONVIF clients and monitor for unusual service crashes.

Description

TP-Link Tapo C500 v2.0 contains an out-of-bounds stack write vulnerability in its ONVIF PTZ SOAP handlers. An authenticated ONVIF client can submit an excessive number of preset-related elements, causing writes beyond the bounds of fixed-size stack arrays and resulting in a crash of the affected service. Successful exploitation may allow an authenticated attacker to cause the affected service to crash, resulting in a denial-of-service condition. Repeated exploitation may repeatedly disrupt camera management and PTZ-related functionality until the service recovers or restarts.

References

Community reviews

Loading reviews…