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).
0.3%(unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306Missing Authentication for Critical Functionality
Show the promptExplain CVE-2026-114357 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114357?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114357?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114357 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
dji:crystalsky zs600c
Versions
From the CNA's record in the CVE List.
Product
Affected
DJI CrystalSky ZS600C
from 0.3.9.7 through 0.6.6.9
Attack patterns (CAPEC)
CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-166 Force the System to Reset Values Severity: Medium