# CVE-2026-50101: Naxclow IoT Platform Not using password aging

> Attackers with exposed relay credentials can maintain persistent access to Naxclow IoT devices, enabling long-term impersonation and interception.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-x3mh-94rm-26c7

## What is CVE-2026-50101?

CVE-2026-50101 is a critical vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Naxclow devices use a server-side, per-device relay credential that never rotates and is re-issued to the device on each boot. Because this credential remains valid indefinitely and cannot be reset or revoked by the legitimate owner, any party that obtains it through any exposure path can maintain persistent access to the device’s relay channel. This enables long-term impersonation or interception, even after factory resets or re-onboarding.

Weakness: CWE-262 (Not Using Password Aging)

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


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

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

## Is CVE-2026-50101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50101 is a critical vulnerability in Naxclow Smart Doorbell X3, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50101 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-50101/ (Markdown: https://insights.sbomify.com/CVE-2026-50101/index.md)
```

## Sources

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

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