# CVE-2026-50099: Naxclow IoT Platform Insertion of sensitive information into Externally-Accessible file or directory

> Attackers with physical access can extract WiFi credentials and firmware via exposed UART console, enabling further compromise of Naxclow IoT devices.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:P/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:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-ccf8-539p-4gc2

## What is CVE-2026-50099?

CVE-2026-50099 is a medium-severity vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

During WiFi association, Naxclow device firmware prints the host network’s SSID, PSK, and negotiated WPA keys in cleartext to an exposed UART console on production hardware. The UART pads are labeled, run with default serial settings, and drop to an interactive RT-Thread shell that permits arbitrary memory reads, enabling full firmware extraction. An attacker with brief physical access, common for outdoor-mounted devices, can therefore recover WiFi credentials and bootstrap firmware-side attacks.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

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


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

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

## Is CVE-2026-50099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50099 is a medium-severity vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 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-50099 in the wild and no public exploit code.

Affected product: Naxclow Smart Doorbell X3. 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-50099/ (Markdown: https://insights.sbomify.com/CVE-2026-50099/index.md)
```

## Sources

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

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