Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege platform account
-
ExploitEnumerate other users' device IDs
-
ExecutionSend OpenAPI config request without ownership check
-
ImpactModify victim device settings or trigger behavior
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated account on the Meari IoT Cloud Platform OpenAPI Service (PR:L) - exploitation is not possible for fully unauthenticated outsiders. Given that precondition, no further special configuration is needed: any logged-in user can invoke OpenAPI calls against devices they do not own because the service omits ownership/permission verification (CWE-862). No user interaction is required (UI:N) and the attack is network-reachable (AV:N). The primary limiting factor is the need to obtain platform credentials; impact is bounded to device integrity (altering settings/triggering behaviors), with no direct confidentiality or availability effect per the CVSS vector. |
| Impact | This is a moderate-severity authorization flaw (CWE-862, Missing Authorization) in the Meari IoT Cloud Platform OpenAPI Service, with a vendor/ICS-CERT CVSS 4.0 base score of 6.3. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates network-reachable, low-complexity exploitation requiring only low privileges - i.e., any authenticated platform user (PR:L) can abuse the flaw against devices they do not own. Impact is narrow and integrity-focused: the vector rates subsequent-system integrity high (SI:H) while confidentiality and availability are rated none (VC:N/VI:N/VA:N/SC:N/SA:N), matching a description centered on unauthorized configuration changes rather than data theft or outages. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so exploitation is not confirmed in the wild and there is no evidence of mass exploitation probability - this limits real-world urgency relative to the CVSS number. The combination of low attack complexity plus a low authentication barrier means exploitation is technically easy for anyone who can register/obtain a platform account, so this is a genuine (not purely theoretical) issue, but the absence of KEV/POC/EPSS signals and the integrity-only, device-scoped impact place it as a real-but-not-emergency priority. Note the input Tag 'Authentication Bypass' conflicts with the actual mechanism: PR:L and CWE-862 describe an authorization (post-authentication) flaw, not an authentication bypass - verify categorization with the CISA ICS advisory. |
| Exploit ScenarioDerived | An attacker registers or already holds a legitimate low-privilege account on the Meari IoT Cloud Platform, then issues OpenAPI requests referencing device identifiers belonging to other customers. Because the service does not verify ownership, the attacker alters those devices' settings or triggers unintended behaviors. No public exploit code was identified at time of analysis, but given AV:N and AC:L the request manipulation is straightforward for any authenticated user. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Missing ownership and permission verification in the Meari IoT Cloud Platform OpenAPI Service lets any holder of a valid platform account alter the configuration of devices they do not own, enabling unauthorized setting changes and unintended device behavior. The flaw is CWE-862 (Missing Authorization) with a vendor/ICS-CERT CVSS 4.0 base score of 6.3; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) confirms network reachability and high integrity impact, but exploitation requires an authenticated account (PR:L) and has no direct confidentiality or availability effect. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV; the low attack complexity and multi-tenant nature of the service nonetheless make it attractive to any legitimate-but-malicious tenant.
RemediationAI
No vendor-released patch identified at time of analysis: neither the Meari download center (https://www.meari.com/en/downLoadCenter) nor ICS-CERT advisory ICSA-26-274-06 (https://www.cisa.gov/news-events/ics-advisories/icsa-26-274-06) provides an exact fixed version in the supplied data, so verify current patch status directly with Meari and apply any update as soon as it is published. Until then, the primary compensating control is server-side enforcement of object-level authorization on every OpenAPI call that reads or writes device configuration - each request must be checked against the caller's identity and explicit ownership or grant for that specific device ID; this is a platform-operator action and, if implemented strictly, will break any legitimate workflow that relied on cross-account device access, so inventory those integrations first. Where platform-side fixes cannot be made immediately, restrict control-plane access by narrowing API token scopes to a single tenant or device set, disabling or firewalling configuration-write endpoints from untrusted networks, and requiring re-authentication or approval for high-impact device settings; each of these reduces exposure but degrades legitimate remote-management functionality and may disrupt third-party integrations. Monitor API logs for configuration changes issued by users to device IDs outside their known account inventory, since that pattern is the clearest detection signal for exploitation of this flaw.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a cloud-hosted OpenAPI/REST service that manages Meari-connected IoT devices across tenant accounts. The underlying defect is CWE-862, Missing Authorization: individual API operations that mutate device configuration are reachable by any authenticated principal, but the service does not verify that the caller owns or has been granted rights to the target device identifier. This is a classic broken object-level authorization pattern in a multi-tenant IoT backend, where authorization is effectively delegated to the API gateway or session layer while the resource-level check is absent. The supplied CPE string, cpe:2.3:a:meari:iot_cloud_platform_openapi_service:*:*:*:*:*:*:*:*, uses a wildcard version, so no specific fixed or vulnerable build is identified in the available data and the entire service line must be treated as potentially affected unless the vendor states otherwise. Public reporting originates from CISA ICS-CERT advisory ICSA-26-274-06, which classifies the issue as an ICS/OT-adjacent authentication bypass affecting the cloud control plane rather than the device firmware itself.
Know when Iot Cloud Platform Openapi Service gets its next vulnerability
- 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N
Network OpenAPI reachable with any low-privilege account (AV:N/AC:L/PR:L); impact is unauthorized integrity changes to device configs only, so I:H with C:N/A:N.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
DescriptionCVE.org
The Meari IoT Cloud Platform OpenAPI Service is vulnerable to an authorization flaw that allows authenticated users to manipulate the configurations of devices they do not own. This vulnerability enables attackers to perform unauthorized actions, such as altering device settings or triggering unintended behaviors, without verifying ownership or permissions.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-91746
GHSA-xj5r-68hv-vxqx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB