Naxclow IoT Platform Authorization bypass through User-Controlled key
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.
Summary
A flaw in Naxclow's platform’s onboarding workflow allows an attacker to replay a confirm-then-bind sequence to silently reassign a device to an arbitrary account. Because the affected endpoints validate request signatures but do not confirm legitimate ownership, an attacker with any account can take over a device without user interaction while the device remains online and unaware.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-42947
- 2026-10-03 Alias added: GHSA-hrr2-8g8j-2h2h
- 2026-10-25 Priority changed: MEDIUM → LOW
References
More Naxclow vulnerabilities
- TI-2026-22948 Naxclow IoT Platform Use of hard-coded cryptographic key CVSS 4.0CRITICAL 9.2
- TI-2026-36892 Naxclow IoT Platform Missing Authorization CVSS 4.0HIGH 8.7
- TI-2026-36888 Naxclow IoT Platform Not using password aging CVSS 4.0CRITICAL 9.2
- TI-2026-36993 Naxclow IoT Platform Missing Authorization CVSS 4.0MEDIUM 6.9
- TI-2026-31129 Naxclow IoT Platform Generation of Predictable Numbers or Identifiers CVSS 4.0MEDIUM 6.9
- TI-2026-36886 Naxclow IoT Platform Insertion of sensitive information into Externally-Accessible file or directory CVSS 4.0MEDIUM 5.1
Sources
- CVE-2026-42947 · CVE Program
- CVE-2026-42947 · NVD
- FIRST EPSS
- GHSA-hrr2-8g8j-2h2h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences