# CVE-2026-100420: Information disclosure vulnerability in the cloud-client daemon of Deco BE63


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-fjpw-4x7c-9fcw

## What is CVE-2026-100420?

CVE-2026-100420 is a medium-severity vulnerability in TP-Link Systems Inc. Deco BE63 V2.0, published on 21 Oct 2026. 

### Official description

A sensitive information disclosure vulnerability in the cloud-client daemon of Deco BE63 allows authenticated attackers to retrieve the plaintext TP-Link ID account password. 

Successful exploitation may allow attackers to compromise the associated cloud account and perform unauthorized actions on behalf of the affected user.

Weakness: CWE-202 (Exposure of Sensitive Information Through Data Queries)

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


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

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

## Is CVE-2026-100420 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100420 is a medium-severity vulnerability in TP-Link Systems Inc. Deco BE63 V2.0, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-100420 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Deco BE63 V2.0. 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-100420/ (Markdown: https://insights.sbomify.com/CVE-2026-100420/index.md)
```

## Sources

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

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