Skip to main content

eSeeCloud CVE-2026-97858

| EUVDEUVD-2026-102879 MEDIUM
Improperly Controlled Modification of Dynamically-Determined Object Attributes (CWE-915)
2026-10-16 ics-cert@hq.dhs.gov GHSA-gcrq-xr3r-v2g8
6.9
CVSS 4.0 · Vendor: hq
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach eSeeCloud service over network
  2. Delivery
    Submit device rebind request for target
  3. Exploit
    Server unbinds legitimate owner
  4. Execution
    Device rebound to attacker account
  5. Impact
    Harvest full device serial ID

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V4 - API and Web Service Object attribute protection
Exploitation Conditions

The target device must be managed through the eSeeCloud cloud platform's device bind/unbind workflow; the flaw is that the server performs an ownership rebind without validating that the requester currently owns the device, so exploitation works even when the device is actively bound to a different account (CWE-915, improperly controlled modification of object attributes). No special configuration, authentication, or user interaction is required per the CVSS vector (PR:N/UI:N/AC:L). The practical limiting factor is that the attacker must be able to reach the cloud service and address a specific target device (e.g., know or enumerate its binding identifier); impact is bounded to ownership takeover and disclosure of the device serial ID rather than broader data access.

Impact

This is a medium-severity information disclosure/integrity-of-ownership issue (CVSS 4.0 base 6.9) in the eSeeCloud device-management platform, disclosed via CISA ICS advisory ICSA-26-288-02. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated attack with no user interaction, and the impact metrics (VC:L/VI:N/VA:N) scope the damage to a LOW confidentiality impact only - specifically leakage of a device's full serial ID - with no integrity or availability impact recorded despite the fact that the attacker also forcibly re-binds the device to their own account (an ownership change the vector arguably under-weights on VI). Exploitation signals are weak-to-absent: there is no CISA KEV listing, no POC, and no EPSS value supplied, so there is no public exploit identified at time of analysis. The realistic priority is MODERATE: the unauthenticated network attack surface and low complexity make it attractive, but the confirmed impact is limited to serial-ID disclosure and ownership hijack of IoT/OT camera-class devices rather than direct code execution or data-at-rest compromise. Note a conflict worth verifying with the vendor: the mechanism (unbinding a device from another owner and rebinding it to the attacker) is a device-takeover/ownership-integrity problem, yet the CVSS sets VI:N and the only tag is 'Information Disclosure' - the real-world impact may be broader than a pure disclosure classification implies.

Exploit ScenarioDerived

An attacker interacts with the eSeeCloud cloud service over the network and issues a device bind request for a target device that is already registered to a legitimate owner; the server unbinds it from that owner and binds it to the attacker's account, returning the device's full serial ID. No authentication to the victim's account, no user interaction, and no POC are required or known. With the serial ID and new binding, the attacker can enumerate or assert control over the targeted device.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 16, 2026

Device ownership takeover and serial ID disclosure in the eSeeCloud cloud platform lets unauthenticated remote attackers rebind a target device to their own account even when that device is actively bound to a different owner, exposing the device's full serial ID. The flaw is server-side only: the bind/unbind workflow accepts the rebind request without verifying that the requester currently owns the device, so no credentials, configuration change, or user interaction are required (CVSS 4.0 base 6.9, AV:N/AC:L/PR:N/UI:N, C:L; assessed CVSS 3.1 6.5 with I:L as well). It was reported to CISA by ICS-CERT as advisory ICSA-26-288-02 and is classified as an information disclosure issue; there is no indication of confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis.

RemediationAI

No vendor-released patch, fix version, or workaround is identified in the available data, so treat the status as 'No vendor-released patch identified at time of analysis' and confirm directly with the vendor and the CISA advisory ICSA-26-288-02 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-288-02) before relying on a release. Until a server-side fix adds per-request ownership validation to the bind/unbind path, apply compensating controls: restrict network reachability to the eSeeCloud binding APIs (the platform itself and any device-management endpoints) so only trusted networks or VPN clients can reach them - the trade-off is that remote device onboarding and mobile app use will fail or require VPN setup, and per CISA ICS guidance remote access should be brokered through a VPN rather than exposing services directly. On the device/network side, segment IoT cameras from general corporate or home networks and block inbound/outbound traffic to the management service from hosts that do not require it, accepting that cloud-based viewing and alerts will be degraded. Operationally, enable and monitor logs for unexpected rebind/unbind events and for devices appearing under unfamiliar accounts, since detecting takeover after the fact is the main available detection; account hardening (strong unique credentials, MFA where the platform supports it) reduces lateral risk from any leaked account data but does not fix the missing authorization check. Because the vulnerability discloses serial IDs, treat exposed serials as potentially compromised identifiers and avoid relying on serial-based trust or recovery flows until the vendor resolves the issue. If the vendor later publishes a fixed backend version or app release, prioritize that upgrade and verify that binding requests without a valid ownership proof are rejected.

Affected VersionsENISA

EseeCloud App 0 ≤4.9.6
EseeCloud Firmware 0 ≤4.9.86.0

Affected Packages

euvd eseecloud_app no fix
euvd eseecloud_firmware no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability maps to CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes - the mass-assignment class in which a server accepts client-supplied object fields and applies them to a persisted entity without binding each field to an authorization check. In eSeeCloud's device-management backend, device ownership is represented as an attribute of a device/binding object; the bind and unbind endpoints apparently trust the caller-supplied device identifier and owner/account reference and write the new owner directly, so an attacker who can address a specific device (by knowing or enumerating its binding identifier or serial) can reassign it. Because the ownership attribute is updated before or without an ownership-validation step, the operation succeeds even when the device is bound to a different account - the classic broken-object-level-authorization plus mass-assignment combination in IoT consumer cloud services, where devices are provisioned to accounts and the cloud maintains the authoritative binding state. The downstream consequence is information disclosure: ownership transfer grants the attacker access to the device's own metadata, including its full serial ID, which is the identifier used for support, registration, and often for further API calls. This is a cloud platform/service issue rather than a firmware issue - the affected surface is the eSeeCloud device bind/unbind API and the accounts/devices it manages, reached over the network with no authentication per the CVSS vector (PR:N).

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (hq) PRIMARY 6.9 MEDIUM
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
vuln.today AI 6.5 MEDIUM

Network, unauthenticated, no UI per the source vector; C:L for serial-ID disclosure and I:L added because the attack also alters device ownership binding, with no availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (hq).

CVSS VectorVendor: hq

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Low
eSeeCloud IoT/OT camera cloud platform, niche vendor-specific deployment footprint
Threat Intel
1
1 sources
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat Yes
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: +10
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Threat IntelligenceMISP

CISA Advisories
Sources: CISA (public domain), CISA Vulnrichment

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy