# CVE-2026-114357: DJI CrystalSky ZS600C ships ADB without authentication (ro.adb.secure=0)


- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-826v-5gj2-v5c8

## What is CVE-2026-114357?

CVE-2026-114357 is a high-severity vulnerability in DJI CrystalSky ZS600C, published on 23 Oct 2026. 

### Official description

Missing authentication for a critical function in the Android Debug Bridge daemon (adbd) in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 allows an attacker to obtain an unauthenticated shell (uid 2000), a foothold for privilege escalation to root. The device ships with ro.adb.secure=0 (no host key authorization) and USB ADB enabled by default; ADB over TCP is not enabled by default but, once enabled (e.g. via the shipped /system/bin/adbd_tcp.sh or 'setprop persist.adb.tcp.port 5555'), the same unauthenticated shell is reachable over the network (CVSS 4.0 base 9.3).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-114357 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114357 is a high-severity vulnerability in DJI CrystalSky ZS600C, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114357 in the wild and no public exploit code.

Affected product: DJI CrystalSky ZS600C. 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-114357/ (Markdown: https://insights.sbomify.com/CVE-2026-114357/index.md)
```

## Sources

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

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