Description
Naxclow devices use a uniform request-signing scheme based on a hard-coded, platform-wide salt embedded in every firmware image. Once this salt is recovered from any device, an attacker can generate valid signatures for arbitrary device or account operations due to the absence of per-device keys, server-side nonce tracking, or replay protections. Combined with the system’s use of plain HTTP for control-plane traffic, the construction enables broad request forgery and impersonation across the platform.
Published: 2026-06-12
Score: 9.2 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The code that signs requests on Naxclow devices relies on a single, hard‑coded cryptographic salt that is embedded in every firmware image. Because the same salt is used across all units, once an attacker recovers it from a single device they can compose valid signatures for any device or account operation. The system provides no per‑device keys, no server‑side nonce checking, and no replay protection, so forged requests are authenticated and accepted. This flaw allows broad request forging and impersonation, effectively giving an attacker remote command and code execution capability or privilege escalation on the affected devices.

Affected Systems

Naxclow Smart Doorbell X3, Naxclow V720, Naxclow X Smart Home, and Naxclow ix cam are the products listed as impacted. No specific firmware or software versions are supplied, so the entire model series may be vulnerable.

Risk and Exploitability

The CVSS score of 9.2 signals a high‑severity flaw, the EPSS score is not available, and the vulnerability is not currently listed in the CISA KEV catalog. Based on the description, the likely attack vector is through the device’s plain HTTP control‑plane traffic, meaning an adversary with network access could interact with the devices. If an attacker manages to extract or guess the shared salt, they can forge authenticated requests that the device will accept. Because the weakness lies in the cryptographic design rather than an implementation bug, exploitation does not require complex inputs, but it does require the attacker to recover or guess the salt. Consequently, the risk of compromise is high, especially for devices exposed to untrusted networks.

Generated by OpenCVE AI on June 12, 2026 at 19:26 UTC.

Remediation

Vendor Solution

Naxclow did not respond to CISA's attempts to coordinate these vulnerabilities. Users should contact Naxclow for more information.


OpenCVE Recommended Actions

  • Contact Naxclow for guidance and firmware updates.
  • Block or replace the device’s HTTP control‑plane traffic with HTTPS or firewall rules to restrict exposure until a secure update is installed.
  • Apply any vendor‑issued firmware patches that remove the hard‑coded salt and enforce per‑device cryptographic keys.

Generated by OpenCVE AI on June 12, 2026 at 19:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 12 Jun 2026 20:45:00 +0000

Type Values Removed Values Added
First Time appeared Naxclow
Naxclow ix Cam
Naxclow smart Doorbell X3
Naxclow v720
Naxclow x Smart Home
Vendors & Products Naxclow
Naxclow ix Cam
Naxclow smart Doorbell X3
Naxclow v720
Naxclow x Smart Home

Fri, 12 Jun 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 12 Jun 2026 18:45:00 +0000

Type Values Removed Values Added
Description Naxclow devices use a uniform request-signing scheme based on a hard-coded, platform-wide salt embedded in every firmware image. Once this salt is recovered from any device, an attacker can generate valid signatures for arbitrary device or account operations due to the absence of per-device keys, server-side nonce tracking, or replay protections. Combined with the system’s use of plain HTTP for control-plane traffic, the construction enables broad request forgery and impersonation across the platform.
Title Naxclow IoT Platform Use of hard-coded cryptographic key
Weaknesses CWE-321
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Naxclow Ix Cam Smart Doorbell X3 V720 X Smart Home
cve-icon MITRE

Status: PUBLISHED

Assigner: icscert

Published:

Updated: 2026-06-12T19:02:26.665Z

Reserved: 2026-06-08T20:04:55.536Z

Link: CVE-2026-28742

cve-icon Vulnrichment

Updated: 2026-06-12T19:02:23.347Z

cve-icon NVD

Status : Received

Published: 2026-06-12T19:16:26.743

Modified: 2026-06-12T19:16:26.743

Link: CVE-2026-28742

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-12T20:19:26Z

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key