{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105664 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105664 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."},"fix_prompt":"Check this codebase for CVE-2026-105664 and fix it if it is affected.\n\nWhat it is: CVE-2026-105664 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.\nExploitation: There is no known exploitation of CVE-2026-105664 in the wild and no public exploit code.\n\nAffected 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105664/ (Markdown: https://insights.sbomify.com/CVE-2026-105664/index.md)","id":"CVE-2026-105664","markdown":"https://insights.sbomify.com/CVE-2026-105664/index.md","name":"CVE-2026-105664","record":{"aliases":["GHSA-cm9q-hmj5-h2w5"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"EseeCloud IoT platform","requires_auth":"none","summary":"An attacker with a valid token can enumerate registered devices by observing response discrepancies, exposing device inventory information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"The endpoint exposes an observable response discrepancy when processing ID values. A request submitted with a nonexistent ID returns a distinct error response code from one submitted with a valid, registered ID, allowing an attacker holding a valid access token - but without further authentication or authorization - to distinguish valid ID values from the full 10-digit numeric search space. Combined with the absence of meaningful rate limiting on this endpoint, this discrepancy constitutes an enumeration oracle, enabling an attacker to discover registered devices at scale.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Guangzhou Juan IoT Technology EseeCloud Observable Response Discrepancy","id":"CVE-2026-105664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"J4Care dcm4che Missing Authentication for Critical Function","id":"CVE-2026-105667"},"packages":[],"prev":{"headline":"Gitea panic on the repositories route of individual users","id":"CVE-2026-105661"},"products":["EseeCloud App","EseeCloud Firmware"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Guangzhou Juan IoT Technology Co., Ltd."]},"summary":"An attacker with a valid token can enumerate registered devices by observing response discrepancies, exposing device inventory information.","url":"https://insights.sbomify.com/CVE-2026-105664/"}