# CVE-2026-97858: Guangzhou Juan IoT Technology EseeCloud Improperly Controlled Modification of Dynamically-Determined Object Attributes

> Attackers can unbind IoT devices from legitimate owners and rebind them to their own accounts, gaining full device control and serial ID access.

- **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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-gcrq-xr3r-v2g8

## What is CVE-2026-97858?

CVE-2026-97858 is a medium-severity vulnerability in Guangzhou Juan IoT Technology Co., Ltd. EseeCloud App, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker can cause the server to unbind the target device from its current owner and rebind it to the requesting account, regardless of whether the device is currently bound to a different account, allowing an attacker to obtain the device's full serial ID.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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


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

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

## Is CVE-2026-97858 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97858 is a medium-severity vulnerability in Guangzhou Juan IoT Technology Co., Ltd. EseeCloud App, published on 16 Oct 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-97858 in the wild and no public exploit code.

Affected product: Guangzhou Juan IoT Technology Co., Ltd. EseeCloud App. 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-97858/ (Markdown: https://insights.sbomify.com/CVE-2026-97858/index.md)
```

## Sources

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

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