CVE-2026-50101 — Naxclow IoT Platform Not using password aging
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Naxclow Ix Cam, Naxclow Smart Doorbell X3, Naxclow V720…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Naxclow | Ix Cam | version All | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Naxclow | Smart Doorbell X3 | version All | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Naxclow | V720 | version All | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Naxclow | X Smart Home | version All | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.2 | CVSS 4.0 | Critical | — | — | ics-cert@hq.dhs.gov via NIST National Vulnerability Database |
| 9.2 | CVSS 4.0 | Critical | — | — | icscert via CVE Program (cve.org) e CISA ADP |
| 8.1 | CVSS 3.1 | High | 2.2 | 5.9 | ics-cert@hq.dhs.gov via NIST National Vulnerability Database |
| 8.1 | CVSS 3.1 | High | — | — | icscert via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ics-cert@hq.dhs.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.42%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · naxclow/smart doorbell x3, naxclow/x smart home, naxclow/v720, naxclow/ix cam
- SSVC assessment updated
- Record published
- CVSS changed · 8.1
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-50099 Naxclow IoT Platform Insertion of sensitive information into Externally-Accessible file or directory Jun 12, 2026
- High CVE-2026-50108 Naxclow IoT Platform Missing Authorization Jun 12, 2026
- Medium CVE-2026-50244 Naxclow IoT Platform Missing Authorization Jun 12, 2026
- Medium CVE-2026-42932 Naxclow IoT Platform Generation of Predictable Numbers or Identifiers Jun 12, 2026
- High CVE-2026-42947 Naxclow IoT Platform Authorization bypass through User-Controlled key Jun 12, 2026
- Critical CVE-2026-28742 Naxclow IoT Platform Use of hard-coded cryptographic key Jun 12, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-50101 is "Naxclow IoT Platform Not using password aging", rated High. It affects Ix Cam (Naxclow); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 0.42% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.