CISA flags flaws in Guangzhou Juan EseeCloud cameras
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CISA advisory details hard-coded credentials, device rebinding, and ID enumeration flaws in EseeCloud IP camera app/firmware that could let attackers hijack devices.
CISA published an ICS advisory covering three vulnerabilities in Guangzhou Juan IoT Technology's EseeCloud app (≤4.9.6) and firmware (≤4.9.86.0), used to manage internet-connected IP cameras deployed worldwide. CVE-2026-107617 involves hard-coded credentials that allow direct attacker login to devices. CVE-2026-97858 allows an attacker to force the server to unbind a device from its legitimate owner and rebind it to an attacker-controlled account regardless of current ownership, exposing the device's full serial ID. CVE-2026-105664 is an observable response discrepancy (CWE-204) on an ID-lookup endpoint combined with lack of rate limiting, letting an authenticated-but-unauthorized attacker enumerate valid 10-digit device IDs across the full registered device population, enabling mass device discovery.
The vendor did not respond to CISA's coordination attempts, so no patches are available; affected users are directed to contact the vendor directly. CISA's only mitigations are generic ICS network hygiene: isolate camera/control system devices from the internet, place them behind firewalls, and use VPNs for remote access. No in-the-wild exploitation has been reported. The vulnerabilities were responsibly disclosed by a researcher from Tokyo University of Science and GMO Flatt Security.
Given the vendor's lack of response and absence of patches, defenders operating EseeCloud cameras should prioritize network segmentation and credential rotation where possible, and treat any internet-exposed device as a high-risk target for account takeover and enumeration-based reconnaissance, pending vendor remediation.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-288-02
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 614 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs