# CVE-2026-105815: Credential Material Exposure Leading to Unauthorized Streamed Media-Session Access in TP-Link Tapo C210

> Unauthenticated attackers can access encrypted media sessions by exploiting exposed shared credentials in the DS JSON API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-j2hx-4c2v-47j3

## What is CVE-2026-105815?

CVE-2026-105815 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C210 v3.6, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TP-Link Tapo
C210 V3.60 may expose shared credential material and cryptographic metadata
through unauthenticated DS JSON API requests. The exposed shared credential can
be accepted by the Streamd Digest authentication mechanism as an administrative
password, allowing an unauthenticated adjacent-network attacker to establish
encrypted media sessions without knowledge of the device account
password.  

Successful
exploitation may disclose credential and cryptographic material and allow
unauthorized access to encrypted media sessions.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-105815?


## How do I fix CVE-2026-105815?

No fix has been published for CVE-2026-105815 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105815 being exploited?

There is no known exploitation of CVE-2026-105815 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105815 and fix it if it is affected.

What it is: CVE-2026-105815 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C210 v3.6, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105815 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Tapo C210 v3.6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105815/ (Markdown: https://insights.sbomify.com/CVE-2026-105815/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105815
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105815
- OSV: https://osv.dev/vulnerability/CVE-2026-105815

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105815/
Summaries are generated and may contain mistakes; the official description above is the record.