# CVE-2026-42932: Naxclow IoT Platform Generation of Predictable Numbers or Identifiers

> Attackers can enumerate active devices by predicting identifiers and accessing the high-water mark endpoint, exposing the fleet size.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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-x87p-mc42-f63g

## What is CVE-2026-42932?

CVE-2026-42932 is a medium-severity 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 device identifiers use fixed manufacturing prefixes combined with sequential counters, producing a fully predictable and enumerable identifier space. Because the platform also exposes an endpoint that reveals the current identifier high-water mark, the active fleet can be enumerated.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2026-42932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42932 is a medium-severity 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-42932 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-42932/ (Markdown: https://insights.sbomify.com/CVE-2026-42932/index.md)
```

## Sources

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

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